Property talk:P5976
Latest comment: 2 years ago by Loominade in topic Lexeme → Sense rather than Sense ↔ Sense
Documentation
false friend
word in another language whose spelling is almost identical but whose meaning is different
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:
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 |
| |||||||||
| Proposal discussion | Proposal discussion | |||||||||
| Current 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, SPARQLConflicts 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
edit@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)