-
Notifications
You must be signed in to change notification settings - Fork 11
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
Could we add metaphor and metonym to the sense links for version1.4? #81
Comments
These sound like useful relations.
We've been linking things both ways for a while, but is it really necessary? Can we not just, e.g., traverse the |
Hmm. So leave looking up the reverse to the tool/library? I think PWN wanted to make a principled difference between those they considered reversible and those not (e.g. entailment). But (i) we could list this somewhere (ideally in the schema: reversible, bidirectional or nothing) and (ii) I want my tool to show the reverse of entailment anyway, ... Some other wordnets (e.g. DanNet) prefer not to list reverse, and it would save space. @jmccrae, @arademaker, @1313ou, @simongray, @piekvossen what do you think? |
Our modelling always includes an inverse property (e.g., hypernym/hyponym) even when it is not necessary. OEWN is another resource that internally drops these inverse properties, but does include them in the XML export. It is well-documented in the GWA Docs which properties are inverse of each other. I don't think this format requires all inverse properties to be included, and individual resources could choose not to include them if they wish. Also @fcbond, I don't think your example of metonymy is actually a metonym. A metonym is 'the use of the name of one thing for that of another of which it is an attribute or with which it is associated', as such I understand at a relationship between two different lemmas not senses of the same lemma. On the proposal overall however though, I think it is a great idea.👍 |
Hi,
Our modelling always includes an inverse property (e.g., hypernym/hyponym)
even when it is not necessary. OEWN is another resource that internally
drops these inverse properties, but does include them in the XML export. It
is well-documented in the GWA Docs which properties are inverse of each
other.
I don't think this format requires all inverse properties to be included,
and individual resources could choose not to include them if they wish.
Also @fcbond <https://github.com/fcbond>, I don't think your example of
metonymy is actually a metonym. A metonym is 'the use of the name of one
thing for that of another of which it is an attribute or with which it is
associated' <https://www.merriam-webster.com/dictionary/metonymy>, as
such I understand at a relationship between two different lemmas not senses
of the same lemma.
I think my use is fairly standard, e.g., from wikipedia " Many cases of
polysemy originate as metonyms: for example, "chicken" means the meat as
well as the animal; "crown" for the object, as well as the institution."
… On the proposal overall however though, I think it is a great idea.👍
--
Francis Bond <https://fcbond.github.io/>
|
I think we should have them go in two directions:
metaphor (from target to source)
_metaphor
is a relation between two senses, where the first sense is a metaphorical extension of the second sense_.has-metaphor (from source to target)
has-metaphor
is a relation between two senses, where the first sense can be metaphorically extended to the second sense.metonym (from source to target)
metonym
is a relation between two senses, where the first sense is a metonymic extension of the second sense.has-metonym (from target to source)
metonym
is a relation between two senses, where the first sense is can be metonymically extended to the second sense.De Luca and Lönneker-Rodman (2008) proposed
extMetaphorOf
andextendedByMetaphor
, but I think the simpler names I propose match the existing relations better.Ernesto William De Luca and Birte Lönneker-Rodman. 2008. Integrating Metaphor Information into RDF/OWL EuroWordNet. In Proceedings of the Sixth International Conference on Language Resources and Evaluation (LREC'08), Marrakech, Morocco. European Language Resources Association (ELRA).
http://www.lrec-conf.org/proceedings/lrec2008/pdf/108_paper.pdf
@rowanhm and I willl have a paper about this in GWC 2025
The text was updated successfully, but these errors were encountered: