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

WordNet lemmas do not contain non-zero causes() and entailments() #2351

Closed
ndo3 opened this issue Jul 31, 2019 · 3 comments
Closed

WordNet lemmas do not contain non-zero causes() and entailments() #2351

ndo3 opened this issue Jul 31, 2019 · 3 comments

Comments

@ndo3
Copy link

ndo3 commented Jul 31, 2019

Hey! I have been trying to look for the causes() and entailments() relationship between verbs like in the WordNet documentation by Christiane Fellbaum, but those functions return no non-empty lists given any lemma. Based on Christiane's documentation, Lemma('kill').causes() should return a list that contains at least one element, 'die'. Is this an unimplemented feature of NLTK WordNet, or is it a bug?

Thanks! :)

@ndo3
Copy link
Author

ndo3 commented Jul 31, 2019

@alvations hey! Sorry I am new to posting issues on Github/NLTK Github page haha so er am I supposed to do anything with the pleaseverify tag? thanks

@alvations
Copy link
Contributor

alvations commented Jul 31, 2019

@ndo3 no worries, the tag is just for any contributors, esp. the WordNet API contributors, to check if the issue raise is a bug or something else. Basically the pleaseverify tag is a "call to check" for other contributors, sometimes we use goodfirstbug too if it looks like an easy fix.

In this case, for this issue, a good way to get faster response from fellow contributors is to show the code lines that are lacking in the code base and check the raw files from WN to see whether those relations exists.

@ekaf
Copy link
Contributor

ekaf commented Jan 20, 2024

While this issue is real, it is only a particular case of issue #1970.

@ekaf ekaf closed this as not planned Won't fix, can't repro, duplicate, stale Jan 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants