Consistency of instance_hypernym
#1044
Labels
change relation
A relations target or source is incorrect or the wrong type of relation is used
validation check
A method should be implemented to verify the validity of the resource
Milestone
We permit
instance_hypernym
s for instances of a class of object, normally referring to named entities of a particular class. Thus it makes sense that such instances should not have further hyponyms and that a synset that is a instance hyponym cannot be a non-instance hyponym as well.There are a few cases where this is broken at the moment
09461312-n
) and "Large Magellanic Cloud" (09359177-n
) are hyponyms of "Magellanic Cloud" (09368400-n
) which is an instance hyponym of "galaxy" (08287963-n
). They should be holonyms.09369905-n
) is a hyponym of "Mediterranean Sea" (09372942-n
). They should be synonyms09529469-n
) has three hyponyms ("Alecto", "Megaera", "Tisiphone") but is an instance hyponym of "mythical creature" (09515254-n
). This should be the other way around ("Alecto" is an instance hyponym of "Fury")09559474-n
) is an instance hyponym, but should be a normal hypernym09595603-n
) has a similar problem to "Fury"08765327-n
) is an instance hyponym of "West Indies" (08764887-n
) and should be a holonym08893374-n
) is a hyponym of "Great Britian" and should be a synonym08907571-n
) and "Jersey" (08907465-n
) are hyponyms of "Channel Island" and should be a holonyms09403029-n
) is hyponym of "gaseous nebula" but it should be a instance hyponym09502368-n
) is a hyponym of "county" but it should be a instance hyponym08489601-n
) should be an instance hyponym of "reform movement"09048869-n
) is a hyponym of "Spain" but should be a holonym09075641-n
) is a hyponym of "Southern United States" but should be a holonymThis issue should also extend the validation to check that
hypernym
andinstance_hypernym
instance_hypernym
cannot be thehypernym
orinstance_hypernym
of any other synsetThe text was updated successfully, but these errors were encountered: