-
Notifications
You must be signed in to change notification settings - Fork 68
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
RelEx & R2L: How fast does it go? #191
Comments
Nevermind, I see there's a similar issue already @ #177 |
There's no verb in this rule because the howdegq() rule only creates the "how fast" constituent. The sentence structure is created by the SV-rule and the "goes fast" by the advmod() rule. I'm not sure whether you're asking about advmod() or the howdegq-rule. I only created the howdegq-rule, but I think the whole output of the verb-phrase should be: advmod(go, fast) in comparison to: advmod(go, fast) I'm saying this without looking at the rules right now, so I hope that's right . . . |
Regarding whether I was asking about advmod-rule or the howdegq-rule, I was including both. When howdegq-rule is triggered on the word "fast", I am sure advmod-rule needs to be excluded. Currently it is not, causing
called with "$qVar" as one of the word. |
Well, actually, what we want is for BOTH rules to be triggered, but by different dependencies, so that (1) the advmod rule creates the r2l link for advmod(go, fast) and (2) the howdegq rule creates the r2l link for what is now represented by advmod(fast, how). The real problem right now is that the advmod(go, fast) relationship is not being created by the semantic algorithms at all for these sentences; I guess it is being pre-empted by the advmod(fast, how). This requires editing of the semantic algorithms. As for the relex2logic rules, then the problem becomes how to prevent the advmod(fast, how) from triggering the advmod rule, which may be impossible since the r2l rules don't accept boolean negation; therefore, I should probably revise the semantic algorithms to create a new dependency relation for (fast, how), instead of _advmod() -- such as _degmod() . .. I will work on that now . . . Did that all make sense to you? |
Humm... I see. I think I see the problem, at least in terms of R2L rules and how exclusion works. With both |
"How fast does it go?" is weird:
RelEx:
I though the first attribute of
_advmod
would always be the verb? Not too sure about this one.RelEx2Logic:
advmod-rule
called with "fast" and "_$qVar", I am sure that is wrong.The text was updated successfully, but these errors were encountered: