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

Ollie sometimes inserts "be" over conjunction edge #19

Open
schmmd opened this issue May 31, 2013 · 2 comments
Open

Ollie sometimes inserts "be" over conjunction edge #19

schmmd opened this issue May 31, 2013 · 2 comments

Comments

@schmmd
Copy link
Member

schmmd commented May 31, 2013

Hi

Having grabbed the latest Ollie JAR which I believe is v1.0.2 I’ve noticed something odd having run a few sentences through it and wondered if you could take a look and confirm whether it’s a bug. I had used an older version before (1.0.0) and ran this sentence through it again to check that version and I don’t see the same oddity.

Here is a simple form of the sentence structure that demonstrates the problem:
The dog has died due to shock and is being buried at home tomorrow.

With Ollie 1.0.0 we get:
0.793: (The dog; has died due to; shock)
0.698: (The dog; is being buried at; home)

But with 1.0.2 we get:
0.673: (The dog; has died is due to; shock)
0.554: (The dog; has is being buried at; home)

Other than the scores changing, its simply the inclusion of the multiple VBZ nodes across the two relations that doesn’t look right. Could you confirm this is unexpected behavior, I couldn’t think of a reason why you might want this to be the case. Sorry if this has already been fixed I haven’t had time to grab the very latest source and build it to test against.

Thanks

Tony

Antony Scerri
Principal Technology Researcher, Elsevier Labs

@schmmd
Copy link
Member Author

schmmd commented Jun 3, 2013

This is an issue from the conjunction-expansion code rewritten a while back.

@schmmd
Copy link
Member Author

schmmd commented Jun 3, 2013

sentence

(MaltParser output)

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