Property talk:P8814

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

WordNet 3.1 Synset ID
Synset identifier in Princeton’s WordNet Version 3.1

Applicable "stated in" value	WordNet (Q533822)
Data type	External identifier
Allowed values	[0-9]{8}-[anprsv]
Example	dog (Q144) → 02086723-n pawl (Q55629301) → 03907626-n hot dog (Q181055) → 07692347-n
Source	https://wordnet.princeton.edu/
See also	Interlingual Index ID (P5063), BabelNet ID (P2581)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P8814 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 30,488 Main statement 30,469 out of 117,000 (26% complete) >99.9% of uses Qualifier 3 <0.1% of uses Reference 16 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8814#Unique value, SPARQL (every item), SPARQL (by value)

Format “[0-9]{8}-[anprsv]”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8814#Format, SPARQL

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8814#Single value, SPARQL

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8814#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase sense (Q54285715), Wikibase lexeme (Q51885771): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P8814#Entity types

Extend this property to be used on Senses

I propose to use this property also on Senses, in order to be able to link to verbs, adjectives, etc. --Denny (talk) 16:52, 18 October 2021 (UTC)

What you suggest would be workable, but there are a couple of issues to consider:

• It's generally better to create new properties for different uses. This makes it easier to write tools that use these properties later. There seems to be a philosophy on Wikidata that it is fine to conflate different meanings of a property so long as they are disambiguated by the type of the subject. This seems to stem from the document-oriented view of Wikidata. From the knowledge graph view, this causes trouble.
• As discussed briefly in the property proposal, I feel it is better to use the concept (Q) item as an intermediary between our lexical items and external concepts, but apparently opinions differ. CC @Eihel

Bovlb (talk) 17:03, 18 October 2021 (UTC)

Thanks for answering @Bovlb:. If no one disagrees within a few days, I think I'll start using it on Senses. The good thing is it will be easily to automatically split it again if needed.

Regarding the second point, we don't have Q-items for many verbs and other POS besides nouns. So for these in particular it would be useful to be able to use the WordNet mapping. --Denny (talk) 18:08, 18 October 2021 (UTC)

 Support Hello Bovlb Hello Denny , During property proposal, as I saw this property in lexemes and senses, it still seems obvious to me. I changed WordNet 3.1 Synset ID (P8814)property constraint (P2302)allowed-entity-types constraint (Q52004125)item of property constraint (P2305)Wikibase lexeme (Q51885771) + Wikibase sense (Q54285715). Cordially. —Eihel (talk) 06:20, 19 October 2021 (UTC)

I would think it is better to have separate identifiers for words, senses and synsets. — Finn Årup Nielsen (fnielsen) (talk) 13:56, 14 February 2024 (UTC)

I deprecated the current and only formatter url because of link rot

I suggest we contact the team responsible for Wordnet and work with them to find a solution. So9q (talk) 04:20, 8 December 2023 (UTC)

I have taken the liberty to contact WordNet. — Finn Årup Nielsen (fnielsen) (talk) 14:08, 14 February 2024 (UTC)