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

Some information about senses is not stored #63

Open
fcbond opened this issue Mar 28, 2019 · 12 comments
Open

Some information about senses is not stored #63

fcbond opened this issue Mar 28, 2019 · 12 comments
Assignees

Comments

@fcbond
Copy link
Member

fcbond commented Mar 28, 2019

I just checked and we are missing a few things from the database:

    324 also_sees
     15 region_domains
     10 topic_domains
    398 usage_domains
   1055 syntactic_marker
      2 verb_groups

NLTK does not read participles, so we are also missing them!

*_domain links to lemmas, but I think it should link to synsets

syntactic markers are for adjectives:

(p) predicate position
(a) prenominal (attributive) position
(ip) immediately postnominal position

I think we should make three new entries (attributive adjective, predicative adjective and postpositive adjective: check Huddleston for names).
Then we could link with exemplifies.
We should cross-check with the ERG

We have no examples of participles (but e.g. elapsed/elapse should be), similar or other.

@goodmami
Copy link
Member

goodmami commented Apr 3, 2019

These syntactic markers, or at least the descriptions, seem rather English-specific. For instance, it is not necessarily the case that attributive adjectives are prenominal (such as in Spanish or French), and it would be odd to have postpositive without prepositive. And even for English, what is the intended use? To mark attributives that cannot vary their position (such as main or ago)?

@fcbond
Copy link
Member Author

fcbond commented Apr 3, 2019 via email

@goodmami
Copy link
Member

goodmami commented Apr 3, 2019

We don;t have prepositive as it is the default in English (so these are marked subtypes)

That is my point. In some other languages postpositive would be the default, so it would be improper, I think, to define a postpositive marker without the option for a prepositive marker, even if you only mark the non-default case on senses for each language.

Or perhaps I'm not understanding what syntactic markers are or what you mean by "make three new entries"...

@fcbond
Copy link
Member Author

fcbond commented Apr 3, 2019 via email

@arademaker
Copy link
Member

Regarding relations , I noted some time ago that some relations are between synsets and senses , but Francis surely know that! Just helping to ensure no data will be lost.

@fcbond
Copy link
Member Author

fcbond commented Apr 3, 2019 via email

@arademaker
Copy link
Member

arademaker commented Apr 3, 2019

Sorry, my mistake. In our paper http://arademaker.github.io/files/gwc-2016-icv.pdf we discussed that range and domain of some relations in the WN docs are not precisely defined (section 5.2).

The following pointer types are usually used to indicate lexical relations: Antonym, Pertainym, Participle, Also See, Derivationally Related. The re- maining pointer types are generally used to represent semantic relations.

But double-checking now, I confirmed that we don't have sense-synset nor synset-sense for them, but we do have both sense-sense and synset-synset.

https://ibm.co/2UeyZhl

@fcbond
Copy link
Member Author

fcbond commented Apr 3, 2019 via email

@arademaker
Copy link
Member

arademaker commented Apr 3, 2019

Ah, that is another way to see. You are saying that the proper translation to RDF would be to propagate some synset1-synset2 relations to all-senses-synset-1 to all-senses-synset-2, is that right?

But as you can see in this other query https://ibm.co/2FY6VGp for the classifiedBy* and frame relations that we mentioned in the article, the sense-sense relations are exceptions

?REL, ?domain, ?range, ?count
classifiedByRegion,WordSense,WordSense,15
frame,WordSense,String,365
classifiedByTopic,WordSense,WordSense,11
classifiedByUsage,WordSense,WordSense,409

Or are you saying that it is in the other way around? That is, some sense-sense relations should be collapsed to synset1-synset2 whenever we confirm that all senses of synset1 are linked to all senses of synset2 by that relation.

@goodmami
Copy link
Member

goodmami commented Apr 4, 2019

We can make the definitions specific to English: (and add a domain link!). I want to NOT have special marker, but just link to synsets.

Ah ok, so map the PWN syntactic marker annotations to OMW sense-synset links.

Still, I can imagine if one sees (postpositive, is_exemplified_by, "ago") they might want to find what is exemplified by "prepositive" as well. It would help if we could negate subqueries, e.g., those items that are not exemplified by "postpositive" (which would include unconstrained and strictly prepositive examples).

@fcbond
Copy link
Member Author

fcbond commented Apr 4, 2019 via email

@arademaker
Copy link
Member

arademaker commented Apr 4, 2019

In Portuguese, the prepositive usually has a figurative meaning and postpositive usually has the literal meaning.

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