Property talk:P5976

Documentation

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

false friend
word in another language whose spelling is almost identical but whose meaning is different

Represents	false friend (Q202961)
Data type	Sense
Domain	Senses (note: this should be moved to the property statements)
Example	According to this template: fourniture (fr) ←→ furniture (en) facet (en) ←→ facet (pl) According to statements in the property: no label (L45433-S1) → no label (L679603-S1) no label (L227426-S1) → no label (L336411-S1) When possible, data should only be stored as statements
See also	said to be the same as (P460), synonym (P5973), translation (P5972), homograph lexeme (P5402)
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 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/P5976 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 130 Main statement 127 97.7% of uses Qualifier 3 2.3% of uses
Search for values

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

Allowed entity types are Wikibase lexeme (Q51885771), Wikibase sense (Q54285715): 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/P5976#Entity types

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

List of violations of this constraint: Database reports/Constraint violations/P5976#Scope, hourly updated report, SPARQL

Conflicts with “instance of (P31)”: this property must not be used with the listed properties and values. (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/P5976#Conflicts with P31, search, SPARQL

Conflicts with “subclass of (P279)”: this property must not be used with the listed properties and values. (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/P5976#Conflicts with P279, search, SPARQL

Symmetric property: if [item A] has this property linked to [item B], then [item B] should also have this property linked to [item A]. (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/P5976#Symmetric, SPARQL

Lexeme → Sense rather than Sense ↔ Sense

@JackPotte, Tubezlob, YULdigitalpreservation, Nepalicoi: I know this property was originally designed to go symmetrically Sense ↔ Sense but please consider that it might be better to use it Lexeme → Sense.

For instance the German Art (L36201) has at least 4 Senses and none of which is any of english art (L12388) or french art (L1348). Sense ↔ Sense would mean, every sense of art (L12388) should be a false friend of every sense in Art (L36201).

I see it like this: The lexeme Art (L36201) has 4 senses and it is often assumed to also have the sense of art (L12388)-S1 because of art (L12388) but it is a false friend. This could be described by a relationship that goes Lexeme → Sense – Loominade (talk) 15:10, 27 July 2022 (UTC)