-
Notifications
You must be signed in to change notification settings - Fork 15
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
Feature request: #auxfun macros (and other #funs too if feasible?) to distinguish word order #23
Comments
Another issue: attachment of modifiers, suppose a phrase like
In #1
AdjCN
( AdvCN ( UseN portion_N )
( PrepNP of_Prep
( DetCN ( DetQuant IndefArt NumSg ) ( UseN building_N ) )
)
)
( PassVAgent separate_V
( DetCN (DetQuant IndefArt NumPl) ( UseN wall_N ) )
): CN[2,3,4,5,6,8]
#LIN: "portion of a building separated by walls"
#2
AdvNP
( DetCN each_Det
( AdjCN ( UseN portion_N )
( PassVAgent separate_V
( DetCN (DetQuant IndefArt NumPl) ( UseN wall_N ) )
)
)
( PrepNP of_Prep
( DetCN ( DetQuant IndefArt NumSg ) ( UseN building_N ) )
): NP[1,2,3,4,5,6,8]
#LIN: "portion separated by walls of a building" However, In any case, I can only imagine that the NP-version of 1 would also be constructed, but it's thrown away before it can be prioritised. And I would like to prioritise it, because the attachment matches the word order: both "building" and "walls" are children of "portion", but in 1, building is more immediately attached. |
I can solve the particular case with an #auxfun that says, every time when a NOUN has an With an explicit Could one make a more fundamental change in the algorithm that wouldn't require explicit instructions about word order? Like ranking higher trees whose subtrees are attached according to distance in the original string. I don't know if this is feasible at all/requires too much rewriting. I can get by with auxfuns, just thinking aloud here. |
Here's a conllu file to test with
|
Current behaviour, it treats phrases like "Section 10" (apposition) and "10 sections" identically.
The text was updated successfully, but these errors were encountered: