Open Wordnet Documentation (ja)

Definition

Core semantic relations that define synsets.

We follow the discussion in [Maziarz:Piasecki:Szpakowicz:2013]

Contribute more examples

Contribute test

Definition

A hyponym of something is its subtype: if A is a hyponym of B, then all A are B.

Examples

• beef is a hyponym of meat
• pear is a hyponym of edible fruit
• dictionary is a hyponym of wordbook

Tests

Test:

• Hyponymy-relation between nouns (EWN test 9)

Conditions:

• both A and B are singular nouns or plural nouns.

Test:

• Hyperonymy/hyponymy between verb synsets (EWN test 11)

Conditions:

• A is a verb in the infinitive form
• B is a verb in the infinitive form
• there is at least one specifying AdvP, NP or PP that applies to the B-phrase.

Comments

This is the fundamental relation, generally used for nouns and verbs. In plWordNet it is also extended to adjectives and adverbs.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="hyponym"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

当該synsetが相手synsetに包含される

Examples

"canis familiaris"(02084071-n)は"domestic animal"(01317541-n)と"canid"(02083346-n)に包含される

Tests

Hyperonymy/hyponymy between verb synsets ([EWN] test 11, p23)

Conditions:

• A is a verb in the infinitive form
• B is a verb in the infinitive form
• there is at least one specifying modifier (AdvP, NP or PP) that applies to the B-phrase

Comments

This is the fundamental relation, generally used for nouns and verbs. In the original Princeton WordNet the name 'troponym' was used for this relation when relating to verbs. In plWordNet it is also extended to adjectives and adverbs.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="hypernym"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A (instance_hyponym) is a type of concept B (instance_hypernym), and where A is an individual entity. A will be a terminal node in the hierarchy. Instances are expressed by proper nouns.

An instance hyponym can also be referred to as a type

Examples

• city has instance_hyponym manchester

Tests

Condition: A is a proper noun (or named entity), B is a common noun.

Comments

Hyponymy is a relation between classes of entities. Individual entities can also be said to belong to some class. Although we do not find many instances in a lexical database, the relation is useful for users that want to add particular instances and do not want to consult a separate database. To distinguish it from class hyponymy the relation is dubbed has_instance.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="instance_hyponym"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A (instance_hyponym) is a type of concept B (instance_hypernym), and where A is an individual entity. A will be a terminal node in the hierarchy. Instances are expressed by proper nouns.

An instance hypernym can also be referred to as a type

Examples

• manchester has instance_hypernym city

Tests

Condition: A is a proper noun (or named entity), B is a common noun.

Comments

Sometimes modelled as hyponomy/hypernymy relations.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="instance_hypernym"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Two words are antonyms if their meanings are opposite in some way such as:

1. The two words show binary opposition: superior vs inferior (simple)
2. The two words are near the opposite ends of a spectrum: hot vs cold (gradable)
3. The two words express change or movement in opposite directions: buy vs sell (converse)

Antonymy can link any two members of any part-of-speech — verbs (e.g. dress vs. undress), adverbs (e.g. naturally vs. unnaturally), adjectives (e.g. superior vs. inferior) and nouns (e.g. catalyst vs. anti-catalyst), but should only ever link concepts with the same part-of-speech.

Antonymy is not transitive: If A is an antonym of B and B an antonym of C, then A is not necessarily and antonym of A. Consider domestic ⇔ national ⇔ international: it does not follow that domestic ⇔ international, or sister ⇔ brother ⇔ sister does not imply sister ⇔ sister.

Examples

• man has antonym woman
• superior has antonym inferior
• buy has antonym sell
• northen has antonym southern
• homosexual has antonym heterosexual
• sister has antonym brother

Tests

Antonym-relation between nouns (EWN 16)

Conditions:

• A and B are singular or plural nouns
• C is a hyperonym of both A and C and within a reasonable, competitive denotational range.

Antonym-relation between verb (EWN 17)

Conditions:

• A is a synset variant in the third person singular form
• B is a synset variant in the third person singular form
• A and B are members of co-hyponym synsets
• there is a hyperonym of A which is opposite to a hyperonym of B
• the situation referred to by A has an addressee and the addressee is the protagonist of the situation referred to by B

Antonym-relation between verbs and adjectives (or adverbs) EWN 20

Conditions:

• A is a verb in the third person singular form
• B is an adjective
• A and B are (XPOS) co-hyponyms

Comments

類語:反意語、反対語、反義語、アントニム、対照語

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="antonym"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="antonym"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

A relation between two concepts where A and B are equivalent concepts but their nature requires that they remain separate.

Equality is a self-reciprocal link (the two directions of this relation share the same meaning) — Concept-A is equal to Concept-B, and Concept-B is equal to Concept-A.

It denotes a special kind full synonimity that allows separation of synonym lemmas in two different synsets. It can occur with any type of part-of-speech.

At the moment, we're currently making use of this in order to isolate chengyu (成语), a traditional four-character Chinese idiom.

Examples

• 一模一样 (70100056-a) EQUALS identical (02068946-a) identical
• (02068946-a) EQUALS 一模一样 (70100056-a)
• people has equal-synonym folks
• cop has equal-synonym policeman
• fiddle has equal-synonym violin
• begin has equal-synonym start

Tests

Equal Synonym-relation between nouns (EWN 1)

Conditions:

• A and B are singular or plural nouns

Equal Synonym-relation between verbs (EWN 2)

Conditions:

• A is a verb in the third person singular form
• B is a verb in the third person singular form
• there are no specifying PPs that apply to the A-phrase or the B-phrase

Comments

In principle all semantically equivalent words should belong to the same synsets (where they can be differentiated by labels on the appropriate usage).

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="eq_synonym"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A and concept B are closely related in meaning but are not in the same synset. Similarity is a self-reciprocal link (the two directions of this relation share the same meaning) — Concept-A is similar to Concept-B, and Concept-B is similar to Concept-A.

This link was originally used to relate adjectives, but we have unconstrained this use, and we're making use of this link to relate all parts-of-speech.

Similarity can be understood as weak synonymy, opposed to the full synonymy that all lemmas in a concept must share. As adjectives are not structured hierarchically (hyponymy/hypernymy) like verbs or nouns, the similarity link helps showing relations between them.

Examples

• instrument has near_synonym tools

Tests

Similar-relation between nouns (EWN 3)

Conditions:

• Cn are hyponyms of A, Cm are hypnyms of B.

Comments

This relation coerces PWN Similar to relation for adjectives, Verb Group relation for verbs and EWN NEAR_SYNONYM for nouns and verbs. In plWN Similarity relation for adjectives to nouns is a unilateral sense relation which is why it is not given in the mappings below.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="similar"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="similar"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

A relation between two concepts where concept A makes up a part of concept B.

Examples

• hat has part-meronym crown
• people has member-meronym person
• water has substance-meronym hydrogen

Tests

Meronymy-relation between nouns (EWN test 21)

Conditions: - A and B are concrete nouns and are interpreted generically.

Comments

This is an unspecified relation that covers all the relations below. This can be computed automatically, it shouldn't be a special relation.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="meronym"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A makes up a part of concept B.

Examples

• eye has part-holonym face
• planet has member-holonym solar system
• kibibyte has part-holonym mebibyte

Tests

Holonymy-relation between nouns

Comments

This is an unspecified relation that covers all the relations below. This can be computed automatically, it shouldn't be a special relation.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="holonym"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A is a place located in concept B.

Examples

• desert has part-meronym oasis

Tests

Location meronymy -relation between nouns (EWN test 26)

Conditions:

• A is a concrete noun
• B is a concrete noun

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="mero_location"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B is a place located in concept A.

Examples

• space has part-holonym aerospace

Tests

Location meronymy -relation between nouns (EWN test 26)

Conditions:

• B is a concrete noun
• A is a concrete noun

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="holo_location"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A is a member/ element of concept B. Meronym and Holonym Membership is a paired relation that denotes group formation and membership. Is different from hyponym as it does not relates a sub-kind of a concept. It links groups to members — Many instances of Concept-A form Concept-B; and Concept-B is composed of many members of Concept-A.

Examples

• fleet has member-meronym ship

Tests

Member meronymy -relation between nouns (EWN test 22)

Conditions:

• A is a single object-denoting noun
• B is a multiform noun (either a group-noun, a collective-noun or as a lexicalized plural denoting multiple objects)
• preferably humans, animals, plants or vehicles or closed sets such as the number system, or the alphabet.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="mero_member"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B is a member/ element of concept A. Meronym and Holonym Membership is a paired relation that denotes group formation and membership. Is different from hyponym as it does not relates a sub-kind of a concept. It links groups to members — Concept-B is composed of many members of Concept-A; and many instances of Concept-A form Concept-B.

Examples

• ship has member-holonym fleet

Tests

Member holonymy -relation between nouns (EWN test 22)

Conditions:

• B is a multiform noun (either a group-noun, a collective-noun or as a lexicalized plural denoting multiple objects)
• A is a single object-denoting noun
• preferably humans, animals, plants or vehicles or closed sets such as the number system, or the alphabet.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="holo_member"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A is a component of concept B. Meronym and Holonym Part is a paired relation that denotes proper parts (separable, in principle), which preserve a belonging relation even if the physical link is broken — Concept-A can be separated into Concept-B”; and Concept-B is a part of some Concept-A.

This relation is also frequently used to denote geographical inclusiveness relations.

Examples

• glove has part-meronym finger

Tests

Meronymy-relation between nouns (EWN test 24)

Condition:

• A and B are concrete nouns denoting objects, there must be several As

Comments

This relation is also frequently used by PWN to denote geographical inclusiveness relations.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="mero_part"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B is the whole of the different component of concept A. Meronym and Holonym Part is a paired relation that denotes proper parts (separable, in principle), which preserve a belonging relation even if the physical link is broken — Concept-A can be separated into Concept-B”; and Concept-B is a part of some Concept-A.

This relation is also frequently used to denote geographical inclusiveness relations.

Examples

• thumb has part-holonym glove

Tests

Holonymy-relation between nouns (EWN test 24)

Condition:

• B and A are concrete nouns denoting objects, B typically includes a larger entity

Comments

The has_holo-part relation typically relates components to their wholes, namely: something which is either topologically or temporally included in a larger entity and which as well bears some kind of autonomy (non-arbitrary boundaries) and a definite function with respect to the whole.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="holo_part"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A is an amount/piece/portion of concept B.

Examples

• Nigeria has part-meronym Abuja

Tests

Portion meronymy -relation between nouns (EWN test 26)

Conditions:

• A and B are substance denoting nouns

Comments

usually portions (as concepts) do not receive a separate lexical item but are realized by sense extension (for instance, there is no lexical item equivalent to “portion of cake”);

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="mero_portion"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B is an amount/piece/portion of concept A

Examples

• Africa has part-holonym Eastern Hemisphere

Tests

Portion holonymy -relation between nouns (EWN test 26)

Conditions:

• B and A are substance denoting nouns

Comments

The whole always pre-exist the portion.Sometimes portions are sufficiently common in a particular language to become lexicalized. These lexical items will be linked to their wholes by means of a has_holo_portion

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="holo_portion"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A is made of concept B. Meronym and Holonym Substance is a paired relation that denotes a higher bound between part and whole. Separating/removing the substance part, will change the whole — Concept-A is made of Concept-B; and Concept-B is a substance of Concept-A”.

Examples

• paper has substance-meronym cellulose
• wood has substance-meronym lignin

Tests

Substance meronymy -relation between nouns (EWN test 25)

Conditions:

• A is a concrete object
• B is a concrete substance

Comments

There are two basic ways of viewing entities in the world, namely either as an individuated thing or as the stuff from which they are made of. This way, for instance a book can be alternatively named “a book” or “paper”. The relation between things and the stuff which compose them is called MADE_OF.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="mero_substance"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B is made of concept A. Meronym and Holonym Substance is a paired relation that denotes a higher bound between part and whole. Separating/removing the substance part, will change the whole — Concept-A is made of Concept-B; and Concept-B is a substance of Concept-A”.

Examples

• wood has substance-holonym beam

Tests

Substance holonymy -relation between nouns (EWN test 25)

Conditions:

• B is a concrete substance
• A is a concrete object

Comments

Complex holonyms can also contain substances but in that case the MADE_OF relation is used.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="holo_substance"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

This is used for semantic relation types not currently supported by the OMW DTD. The exact relation type can be given with dc:type:

<SynsetRelation relType="other" dc:type="emotion" target="example-en-1234-n"/>

Examples

• curator other museum
• priest other church
• mailman other post office
• mayor other town hall
• judge other court
• ambassador other embassy
• gardener other garden

Tests

Comments

This has no reverse, as we cannot be sure what the relation is gong to be. However, in most cases we would expect there to be a reverse relation.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="other"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="other"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

‘See Also’ is a self-reciprocal link (the two directions of this relation share the same meaning) — Concept-A relates to Concept-B, and Concept-B relates to Concept-A.

It denotes a relation of related meaning with another concept (going beyond synonymy and similarity).

This link was only used to relate adjectives and verbs in Princeton wordnet, but we have unconstrained this use, and we're making use of this link to relate all parts-of-speech.

Examples

• farmer see also farmland
• learn see also school
• picture see also sculpture
• plant see also flower
• walk see also park

Tests

Comments

This could perhaps be merged with other

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="also"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="also"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

A relation between two concepts where concept B is qualified by concept A.

Examples

• poor state_of have-not
• rich state_of rich person

Tests

State Of - relation between noun (EWN 44)

Conditions:

• B is an adjective/adverb.
• A is a noun.

Comments

In plWordNet it is a relation between lexical units. FCB: isn't this the same as attribute (but split into two directions)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="state_of"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A is qualified by concept B.

A is qualified by B.

Examples

• have-not be in state poor
• rich person be in state rich

Tests

Be In State - relation between adjective/adverb (EWN 44)

Conditions:

• A is a noun.
• B is an adjective/adverb.

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="be_in_state"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B comes into existence as a result of concept A. Entailment is a relation that links two verbs, and it is currently unilateral — Verb-A causes Verb-B, without a reciprocal or tracing link. Causation presupposes/requires that some Verb-B will, inevitably, take place during or after Verb-A (e.g. if Verb-A occurs, then Verb-B will also occur).

While not exclusive to these types of verbs, many verbs that have both a transitive and an intransitive form will frequently be submitted to this relation.

Examples

• kill causes die

Tests

Causes - relation (EWN 36)

Conditions:

• A is a verb in the infinitive form or A is a noun in the singular
• B is a verb in the infinitive form or B is a noun in the singular

Causes - relation between verbs and adjectives (or adverbs) (EWN 37)

Conditions: - A is a verb in the infinitive form - B is and adjective

Comments

EUWN's definition of CAUSES is broader than that of PWN. It seems possible to just absorb PWN's links.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="causes"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A comes into existence as a result of concept B.

Examples

• die is caused by kill

Tests

Is Caused By - relation (EWN 36)

Conditions:

• A is a verb in the infinitive form or A is a noun in the singular
• B is a verb in the infinitive form or B is a noun in the singular

Is Caused By - relation between verbs and adjectives (or adverbs) (EWN 37)

Conditions:

• A is a verb in the infinitive form
• B is and adjective

Comments

The 'is caused by' relation was missing from PWN before.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="is_caused_by"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B takes place during or as part of concept A, and whenever concept B takes place, concept A takes place.

Examples

• sleep has subevent snore

Tests

Subevent - relation between verbs/nouns (a) (EWN 41)

Conditions:

• A is a verb in the gerundive form
• B is a verb in the gerundive form

Subevent - relation between verbs/nouns (b) (EWN 42)

Conditions:

• B is a verb in the gerundive form
• A is a verb in the gerundive form buying consists of paying and other events or processes

Comments

The SUBEVENT relation is very useful for many closely related verbs and appeals more directly to human-intuitions (parallel to part-whole relation of concrete entities).

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="subevent"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A takes place during or as part of concept B, and whenever concept A takes place, concept B takes place.

Examples

• snore is subevent of sleep
• pay is subevent of buy

Tests

Is Subevent Of - relation between verbs/nouns (a) (EWN 41)

Conditions:

• A is a verb in the gerundive form
• B is a verb in the gerundive form

Is Subevent Of - relation between verbs/nouns (b) (EWN 42)

Conditions:

• B is a verb in the gerundive form
• A is a verb in the gerundive form buying consists of paying and other events or processes

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="is_subevent_of"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept A qualifies the manner in which an action or event expressed by concept B takes place.

Examples

• noisily manner of slurp

Tests

Manner Of - relation between verbs/adverb (EWN 43)

Conditions:

• A and B are verbs
• B is the hyperonym of A
• C is an adjective/adverb

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="manner_of"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between two concepts where concept B qualifies the manner in which an action or event expressed by concept A takes place.

Examples

• slurp in manner noisily

Tests

In Manner - relation between verbs/adverb (EWN 43)

Conditions:

• A and B are verbs
• B is the hyperonym of A
• C is an adjective/adverb

Comments

In EuroWordNet, we decided not to differentiate between troponymy and hyponymy but to use the IN_MANNER and MANNER_OF relation in addition to normal hyponymy to make the manner component explicit (if it is significant in the meaning of the verb):

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="in_manner"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between nominal and adjectival concepts where the concept A is an attribute of concept B. ‘Attributes’ is a self-reciprocal link (the two directions of this relation share the same meaning) — Concept-A attributes to Concept-B, and Concept-B attributes to Concept-A.

It denotes a relation between a noun and its adjectival attributes, and vice-versa — for this reason it should only link adjectives to nouns and vice-versa.

Examples

• fertile has attributes fecundity
• fecundity has attributes fertile

Tests

Attribute-relation between nouns and adjectives (EWN 14)

Conditions: - A is a noun in the singular - B is an adjective - there is at least one specifying adverb, NP or PP that applies to the A- phrase or the B-phrase - preferably there is a no morphological link between the noun and the adjective

Comments

In plWN Value_of_the_attribute is a unilateral relation from adjectives to nouns.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="attribute"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between an adjectival concept A (quantifier/determiner) and a nominal (pronominal) concept B.

Contribute more examples

Contribute test

Comments

This would work for features like 'medial' or 'proximal' in pronouns, or 'every' in everybody, or 'male' for male personal pronouns, but not masculine agreeement in gendered languages. This relation will include some things that are now marked as domain usage. (to be corrected soon'ish)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="restricts"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

A relation between nominal (pronominal) concept B and an adjectival concept A (quantifier/determiner).

Examples

• this-a (77000061-a) QUANTIFIES [qant] this-n (77000061-n)
• this-n (77000061-n) QUANTIFIER: [hasq] this-a (77000061-a)

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="restricted_by"
		  target="wn-synset-B"/>
</Synset>

Definition

A concept A used when counting concept B.

English does not really use this relationship, but it is common in many languages, such as Chinese, Japanese or Indonesian. A classifier is a word (or often a bound morpheme) which accompanies a noun in certain grammatical contexts, typically individuation, and generally reflects some kind of conceptual classification of nouns, based principally on features of their referents. Thus a language might have one classifier for nouns representing persons, another for nouns representing flat objects, another for nouns denoting periods of time, and so on. The assignment of classifier to noun may also be to some degree unpredictable, with certain nouns taking certain classifiers by historically established convention.

Note that the in a classifier language a classifier does not introduce a new referent, so we treat it as as non-referential.

Examples

• head classifies cattle
• rasher classifies bacon
• ekor classifiers kucil (Indonesian)
• 匹 classifies 猫 (Japanese)

Contribute test

Comments

This relation was introduced in [DaCosta:Bond:2016]

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="classifies"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Concept B is modified by classifier A when it is counted.

Examples

• 'cattle <https://lr.soh.ntu.edu.sg/omw/omw/concepts/ili/48233>`_ is classified_by head
• bacon is classified_by rasher
• kucil is classified_by ekor (Indonesian)
• 猫 is classified_by 匹 (Japanese)

Contribute test

Comments

This relation was introduced in [DaCosta:Bond:2016]

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="classified_by"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Entailment is a relation that links two verbs, and it is currently unilateral — Verb-A entails Verb-B, without a reciprocal or tracing link. This relation presupposes/requires a semantic restriction in which Verb-B has to take place before or during Verb-A.

Examples

• snore entails sleep

Tests

Comments

A verb A entails B if A cannot be done unless B is, or has been, done.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="entails"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Contribute a definition

Examples

• sleep is entailed by snore

Tests

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="is_entailed_by"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Domain is an underspecified relation between two concepts where Concept B is a Topic (scientific category), Region or Usage pointer of Concept A.

Contribute more examples

Contribute test

Comments

This is an underspecified relation that covers Domain Topic, Domain Region, and Is Exemplified By. As such, it is not specified as a relation directly by wordnets, but a wordnet application may employ it as a general relation covering all its subtypes.

In EuroWordNet, Domain is moved to a separate ontology.(EuroWordNet General Document pp 8–10)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="domain"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

In Domain is an underspecified relation between two concepts where Concept A is a Topic (scientific category, Region or Usage term of Concept B.

Contribute more examples

Contribute test

Comments

This is an underspecified relation that covers Has Domain Topic, Has Domain Region, and Exemplifies. As such, it is not specified as a relation directly by wordnets, but a wordnet application may employ it as a general relation covering all its subtypes.

In EuroWordNet, In Domain is moved to a separate ontology.(EuroWordNet General Document pp 8–10)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="has_domain"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Domain Topic is a relation between two concepts where Concept B is a scientific category (e.g. computing, sport, biology, etc.) of concept A.

Examples

• football is a domain topic of place-kick
• plant is a domain topic of evergreen
• ocean is a domain topic of water

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="domain_topic"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="domain_topic"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Has Domain Topic is a relation between two concepts where Concept A is a scientific category (e.g. computing, sport, biology, etc.) of concept B.

Examples

• place-kick has domain topic of football
• evergreen has domain topic of plant
• water has domain topic of ocean

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="has_domain_topic"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="has_domain_topic"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Domain Region is a relation between two concepts where Concept B is a geographical / cultural domain of concept A.

Examples

• Japan is a domain region of sushi
• England is a domain region of War of the Roses
• Pacific is a domain region of Philippine Sea

Contribute test

Comments

We also agreed to change the name for these (to include both geographical and cultural regions)! But I'm not sure to what...

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="domain_region"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="domain_region"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Has Domain Region is a relation between two concepts where Concept A is a term of the geographical / cultural domain of concept B.

Examples

• sushi has domain region of Japan
• War of the Roses has domain region of England
• Philippine Sea has domain region of Pacific

Contribute test

Comments

We have discussed changing the name for these (as they include both geographical and cultural regions). But we have not yet come up with a good name.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="has_domain_region"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="has_domain_region"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Exemplifies is a relation between two concepts where Concept A is the example of Concept B.

Examples

• wings exemplifies plural form
• Band Aid exemplifies trademark

Contribute test

Comments

The name was changed from "Member of this domain - USAGE" as we found it too different from the standard meaning of domain.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="exemplifies"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="exemplifies"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Is Exemplified By is a relation between two concepts where Concept B is a type of Concept A, such as idiom, honorific or classifier.

Examples

• trademark is exemplified by Band Aid
• plural form is exemplified by wings

Contribute test

Comments

We agreed to change the name for these with Christiane! We propose 'Exemplified_By'.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="is_exemplified_by"
		  target="wn-synset-B"/>
</Synset>

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="is_exemplified_by"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Role is an underspecified relation between two concepts where concept A is typically involved in the action or event expressed by concept B.

Contribute more examples

Tests

Role / Involved as general relation (EWN test 29)

Comments

This is an underspecified relation that covers Agent, Patient, Result, Instrument, Location, Direction, Target Direction, and Source Direction. As such, it is not specified as a relation directly by wordnets, but a wordnet application may employ it as a general relation covering all its subtypes.

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="role"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved is an underspecified relation between two concepts where concept B is the action or event concept A typically involved in.

Contribute more examples

Tests

Role / Involved as general relation (EWN test 29)

Comments

This is an underspecified relation that covers Involved Agent, Involved Patient, Involved Result, Involved Instrument, Involved Location, Involved Direction, Involved Target Direction, and Involved Source Direction. As such, it is not specified as a relation directly by wordnets, but a wordnet application may employ it as a general relation covering all its subtypes.

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Agent is a relation between two concepts where Concept A is the semantic role of the animate entity that instigates or causes the happening of Concept B, typically intentionally.

Examples

• teacher is the agent of to teach

Tests

Agent Involvement (EWN test 28)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="agent"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Agent is a relation between two concepts where concept B is typically the action done by the agent expressed by concept A.

Examples

• to teach involved agent teacher

Tests

Agent Involvement (EWN test 28)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_agent"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Patient is a relation between two concepts where Concept A is the semantic role of an entity that is not the agent but is directly involved in or affected by the happening denoted by Concept B.

Examples

• learner is the patient of to learn

Tests

Patient Involvement (EWN test 29)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="patient"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Patient is a relation between two concepts where Concept B is typically an action or event that the patient expressed by Concept A undergoing.

Examples

• to learn involved patient learner

Tests

Patient Involvement (EWN test 29)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_patient"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Result is a relation between two concepts where Concept A exists as a result only by virtue of the activity denoted by Concept B.

Examples

• crystal is the result of to crystalize
• ice is the result of to freeze

Tests

Result Involvement (EWN test 30)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="result"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Result is a relation between two concepts where concept B comes into existence as a result of concept A.

Examples

• to crystalize involved result of crystal
• to freeze involved result of ice

Tests

Result Involvement (EWN test 30)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_result"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Instrument is a relation between two concepts where Concept A is the semantic role of the entity (usually inanimate) that the agent uses to perform an action or start a process expressed by Concept B.

Examples

• hammer is the instrument of to hammer
• sail is the instrument of to sail
• pen is the instrument of to write
• ink is the instrument of to write
• paper is the instrument of to write

Tests

Instrument Involvement (EWN test 31)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="instrument"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Instrument is a relation between two concepts where concept B is typically the action or event with the usage of instrument expressed by concept A.

Examples

• to hammer involved instrument hammer
• to sail involved instrument sail
• to write involved instrument pen
• to write involved instrument ink
• to write involved instrument paper

Tests

Instrument Involvement (EWN test 31)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_instrument"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Location is a relation between two concepts where concept A is the location where the action or event expressed by concept B takes place.

Examples

• school is the location of to teach
• water is the location of to swim

Tests

Location Involvement (EWN test 32)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="location"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Location is a relation between two concepts where concept B is typically the action or event which takes place in the location expressed by concept A.

Examples

• to teach involved location school
• to swim involved location water

Tests

Location Involvement (EWN test 32)

Comments

In plWordNet it is a relation between lexical units.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_location"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Direction is a relation between two concepts where concept A is typically the direction or location of the action or event expressed by concept B.

Examples

• place is the direction of to pass

Tests

Direction Involvement (EWN test 33)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="direction"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Direction is a relation between two concepts where concept B is typically the action or event with the direction or location expressed by concept A.

Examples

• to pass involved direction place

Tests

Direction Involvement (EWN test 33)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_direction"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Target Direction is a relation between two concepts where Concept A is the place designated as the end (as of a race or journey) of an action or event expressed by Concept B.

Examples

• ground is the target direction of to collapse, to fall heavily
• home is the target direction of to go back

Tests

Target-Direction Involvement (EWN test 35)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="target_direction"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Target Direction is a relation between two concepts where concept B is the the action or event leading to a place expressed by concept A.

Examples

• to collapse, to fall heavily involved target direction ground
• to go back involved target direction home

Tests

Target-Direction Involvement (EWN test 35)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_target_direction"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Source Direction is a relation between two concepts where concept A is the place from where the action or event expressed by concept B begins/starts/happens.

Examples

• the start is the source direction of to race
• ship is the source direction of to debark

Tests

Source-Direction Involvement (EWN test 34)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="source_direction"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Involved Source Direction is a relation between two concepts where concept B is the action or event which begins/starts/happens from a place expressed by concept A.

Examples

• to race involved source direction the start
• to debark involved source direction ship

Tests

Source-Direction Involvement (EWN test 34)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="involved_source_direction"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Role is an underspecified relation between two concepts where Concept A undergoes an action in which Concept B is involved (bidirectional).

Contribute more examples

Contribute test

Comments

This is an underspecified relation that covers Co Agent Patient, Co Patient Agent, Co Agent Instrument, Co Instrument Agent, Co Agent Result, Co Result Agent, Co Patient Instrument, Co Instrument Patient, Co Result Instrument, and Co Instrument Result. As such, it is not specified as a relation directly by wordnets, but a wordnet application may employ it as a general relation covering all its subtypes.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_role"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Agent Patient is a relation between two concepts where Concept B is the patient undergoing an action carried out by Concept A.

Examples

• victim is the co agent patient of criminal

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_agent_patient"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Patient Agent is a relation between two concepts where Concept A carries out an action Concept B undergoing.

Examples

• criminal is the co patient agent of victim

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_patient_agent"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Agent Instrument is a relation between two concepts where Concept B is the instrument used by Concept A in a certain action.

Examples

• guitar is the co agent instrument of guitar player

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_agent_instrument"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Instrument Agent is a relation between two concepts where Concept A carries out an action by using Concept B as an instrument.

Examples

• guitar player is the co instrument agent of guitar

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_instrument_agent"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Agent Result is a relation between two concepts where Concept B is the result of an action carried out by Concept A.

Examples

• pastry is the co agent result of pastry cook

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_agent_result"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Result Agent is a relation between two concepts where Concept A takes an action resulting in Concept B.

Examples

• pastry cook is the co result agent of pastry

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_result_agent"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Patient Instrument is a relation between two concepts where Concept B is the instrument used in an action which Concept A undergoes.

Examples

• bread knife is the co patient instrument of bread

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_patient_instrument"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Instrument Patient is a relation between two concepts where Concept A undergoes an action for which the instrument expressed by Concept B is used.

Examples

• bread is the co instrument patient of bread knife

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_instrument_patient"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Result Instrument is a relation between two concepts where Concept B is an instrument used in an action resulting in Concept A.

Examples

• photograpic camera is the co result instrument of photo

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_result_instrument"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Co Instrument Result is a relation between two concepts where Concept A is the result of an action carried out by the instrument expressed by Concept B.

Examples

• photo is the co instrument result of photograpic camera

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Synset id="wn-synset-A" ili="iXYZ" partOfSpeech="x">
  <SynsetRelation relType="co_instrument_result"
		  target="wn-synset-B"/>
</Synset>

Project-specific Names

Definition

Participle is a relation between two concepts where Concept A is a participial adjective which is drived from Concept B in the form of verb.

Examples

• interesting is the participial of interest
• amazing is the participial of amaze

Contribute test

Comments

These are not linked in the NLTK interface so are not shown in OMW 1.0 (or as far as I can see, anywhere FCB)

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="participle"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Pertainym is a relation between two concepts where Concept A is related or applicable to Concept B. Typically A will be an adjective and B a noun, or A an adverb and B an adjective. It is typically used for adjectives that are morphologically related to the noun they are related to, are not gradable and do not have antonyms. It is also used for nouns that are semantically related but not morphologically related, typically because came from different languages historically, so lunar for moon or arborial for tree.

Examples

• lunar is the pertainym of moon
• naval is the pertainym of navy
• slowly is the pertainym of slow
• English is the pertainym of England
• subclinical is the pertainym of clinical
• clinical is the pertainym of clinic

Contribute test

Comments

This may be specialized further. It includes zero derivations. Gnerally it is used for different syntactic categories that have the same root form and are semantically related. Wordnet does not say which is the baseform, the relationship is fully reversible.

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="pertainym"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Definition

Derivation is a relation between two concept where Concept A is the derivationally related form of Concept B.

Examples

• yearly is the derivation of year
• want(n) is the derivation of want(v)
• provision is the derivation of provide

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="derivation"
		  target="wn-sense-B"/>
 </Sense>

Project-specific Names

Contribute a definition

Contribute more examples

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="simple_aspect_ip"
		  target="wn-sense-B"/>
 </Sense>

Contribute a definition

Contribute more examples

Contribute test

XML

In the XML format for Wordnet LMF the relation should be shown like this:

<Sense id="wn-sense-A" synset="wn-synset-A">
   <SenseRelation relType="simple_aspect_pi"
		  target="wn-sense-B"/>
 </Sense>