Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

percolate features during morphological realisation #7

Open
kowey opened this issue Mar 4, 2013 · 3 comments
Open

percolate features during morphological realisation #7

kowey opened this issue Mar 4, 2013 · 3 comments
Assignees
Milestone

Comments

@kowey
Copy link
Owner

kowey commented Mar 4, 2013

The morphological realisation (built-in) is dumb in that it unifies each pre-terminal node of the derived tree independently with the morphological lexicon.

This is not good, because it does not allow for mutually exclusive realisations:
he hold_s_ the apple vs you hold the apple

Right now, the workaround is to supply the necessary features via the input semantics (morphinfo file), but ideally you should be able to just make it work automatically.

@ghost ghost assigned kowey Mar 4, 2013
@kowey
Copy link
Owner Author

kowey commented Mar 4, 2013

Imported from trac issue 7. Created by kowey on 1970-01-01T01:20:38, last modified: 1970-01-01T01:20:54

@kowey
Copy link
Owner Author

kowey commented Mar 4, 2013

Trac comment by kowey on 1970-01-01 01:20:52:

Alexandre has entry in his lexicon which looks like this:

"chambre" n(?P ! gender:Fem)
semantics:[participant(?P) objType(?P "chambre")]

This represents as alternative workaround to the lack of percolation during morph realisation, which is to supply the morph features through the lexicon.

According to Alex, this is not desirable. The information is redundant with that which is already present in the morphological lexicon.

If we had feature percolation, then this would just work.

@kowey
Copy link
Owner Author

kowey commented Mar 4, 2013

Trac comment by kowey on 1970-01-01 01:20:54:

This is actually quite easy to fix. It's a bug in the new standalone sillymorph package, which unifies each word independtly of the other. The right thing to do is not to mapM on the list monad (we use the list monad for prolog-style non-determinism because each word may have more than one realisation), but to foldM instead, passing in the unification variable substitutions along the way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant