Property talk:P138
Latest comment: 1 day ago by Jerimee in topic Namesake
Documentation
named after
entity or event that inspired the subject's name, or namesake (in at least one language). Qualifier "applies to name" (P5168) can be used to indicate which one
entity or event that inspired the subject's name, or namesake (in at least one language). Qualifier "applies to name" (P5168) can be used to indicate which one
[create Create a translatable help page (preferably in English) for this property to be included here]
Qualifiers “applies to name of subject (P5168), applies to name of object (P8338), series ordinal (P1545), subject named as (P1810), object named as (P1932), quotation (P1683), sourcing circumstances (P1480), language of work or name (P407), name in native language (P1559), named by (P3938), point in time (P585), start time (P580), end time (P582), of (P642), manifestation of (P1557), statement is subject of (P805), statement disputed by (P1310), statement supported by (P3680), nature of statement (P5102), mode of derivation (P5886), subject lexeme (P6254), subject form (P5830), location (P276), country of origin (P495), quantity (P1114), criterion used (P1013), applies to part (P518), uses (P2283), has cause (P828), does not have part (P3113), earliest date (P1319), earliest end date (P8554), latest start date (P8555), subject has role (P2868), object of statement has role (P3831), together with (P1706), author (P50), author name string (P2093), reason for deprecated rank (P2241), reason for preferred rank (P7452), name in kana (P1814), entry in abbreviations table (P8703), native label (P1705), kinship to subject (P1039), statement is regarded as spoiler for (P7528), named after (P138), used by (P1535)”: this property should be used only with the listed qualifiers. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Kōnodai (Q11420858), Agochō Kō (Q108297348)List of violations of this constraint: Database reports/Constraint violations/P138#allowed qualifiers, SPARQL
Allowed entity types are Wikibase item (Q29934200): 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/P138#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P138#Scope, hourly updated report, SPARQL
Check start date qualifier
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P138#Check start date qualifier
(Help)
Violations query:
SELECT ?item { ?item p:P138 [ps:P138 ?named; pq:P580 ?starttime; ]. ?named wdt:P569 ?born. FILTER (?starttime < ?born). }List of this constraint violations: Database reports/Complex constraint violations/P138#Check start date qualifier
Check start date qualifier with baptism date
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P138#Check start date qualifier with baptism date
(Help)
Violations query:
SELECT ?item { ?item p:P138 [ps:P138 ?named; pq:P580 ?starttime; ]. ?named wdt:P1636 ?baptismDate. FILTER (?starttime < ?baptismDate). }List of this constraint violations: Database reports/Complex constraint violations/P138#Check start date qualifier with baptism date
Detect loop of one or two items
Loop is strange. Could detect some mistakes. (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P138#Detect loop of one or two items
Loop is strange. Could detect some mistakes. (Help)
Violations query:
SELECT ?item ?value { ?item wdt:P138 ?value. ?value wdt:P138 ?item. FILTER (?item NOT IN (wd:Q44571)) # false positive: GNU }List of this constraint violations: Database reports/Complex constraint violations/P138#Detect loop of one or two items
Detect loop of three items
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P138#Detect loop of three items
(Help)
Violations query:
SELECT ?item ?value1 ?value2 { ?item wdt:P138 ?value1. ?value1 wdt:P138 ?value2. ?value2 wdt:P138 ?item. FILTER (?item != ?value1) FILTER (?item != ?value2) }List of this constraint violations: Database reports/Complex constraint violations/P138#Detect loop of three items
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||||||||||
Dépendance aux langues / Language dependency
editEnglish: A basic issue with this property is that it is a feature of a word, not of a concept, and is accordingly language-dependent. An example from WD:Bistro is Geneva Lake, usually called "lac Léman" in France :
Français : "Bonjour à tous. Depuis que j'ai découvert cette propriété je ne m'en lasse pas. Cependant elle a une limite d'utilisation. En effet cette propriété dépend principalement de la langue. Par exemple le Lac Léman. Si un anglophone met named after:Genova il aura raison. Mais ce n'est qu'une vérité relative, puisqu'en français le terme lac de Genève est très peu employé. Il doit exister de nombreux autres cas.
--Otourly (talk) 17:05, 27 February 2013 (UTC)"
- English: I agree, this property will cause many problems since it refers to the labels of the item and not the item itself.
- Français : Je suis d'accord, cette propriété peut causer beaucoup de problèmes puisqu'elle fait référence aux labels de l'élément, et non à l'élément soi-même.
- --Gloumouth1 (talk) 12:04, 28 February 2013 (UTC)
- English: Another example is Q4127 : Bodensee in German, Lake Constance in English.
- Français : Un autre exemple : Q4127 : Bodensee en allemand, Lac de Constance en français.
- --Eric-92 (talk) 15:30, 28 February 2013 (UTC)
- English: Maybe the qualifiers could help us later: <Q4127> P138 <Q1800901> qualifier [restriction: "in English", "in French"] AND <Q4127> P138 <Q647622> qualifier [restriction: "in German"]
- Français :Peut-être que les qualifieurs pourraient nous aider à sortir de l'ornière ultérieurement. <Q4127> P138 <Q1800901> qualifieur [restriction: "en anglais", "en français"] ET <Q4127> P138 <Q647622> qualifieur [restriction: "en allemand"]
- --Gloumouth1 (talk) 16:03, 28 February 2013 (UTC)
- Français:mon opinion - on devrait avoir un item pour l'objet géographique, et un item pour chacun de ses noms : un item pour le lac, un item pour le nom français "Lac de Constance", un item pour le nom allemand "Bodensee" etc... En fait on pourrait -et même on devrait- avoir potentiellement un item pour tous les mots : un item pour "Arbre" plus un item pour "Arbre (mot français)", un item pour "Tree (english word)", un item pour "Baum (deutsches Wort)" etc... Une erreur a été d'importer seulement Wikipédia et pas les Wiktionnaires qui sont aussi un projet qui marche bien. La distinction systématique entre le mot et la chose règlerait bien des ambiguïtés.
- English: my opinion - we should have different items for the geographical feature and for each of its names in various languages : with this solution, we would have an item about the lake near Konstanz, but also an item for the French name "Lac de Constance" and an item for the German name "Bodensee" and so on... In fact, we could -we should indeed- have an item for every word in every language : we could have an item for "Tree", the topic of various Wikipedia articles, but also one for "Arbre (mot français)", one for "Tree (english word)", one for "Baum (deutsches Wort)". It was a mistake to import only Wikipedia ; Wiktionaries are generally of good quality and should have been imported too. A systematic distinction between the word and the object would have been possible if we had played it this way from the beginning. Touriste (talk) 17:15, 2 March 2013 (UTC)
- English: I think words as items would be a sensible solution in the long term, but we don't know how long it will take to get implemented... A quick remedy might be to consider this property broader (and more vague), i.e., <subject> has in at least one language a name which is named after <object>. --whym (talk) 15:15, 3 March 2013 (UTC)
- English: Yes, that would probably be a good idea to say "one of the name in one of the languages", because we currently have Big Ben is named after Elizabeth II, which sounds weird in all languages. Actually, Big Ben was officially renamed Elizabeth Tower after Elizabeth II. Any idea for a concise label ? --Zolo (talk) 19:51, 4 March 2013 (UTC) Or maybe, it will be possible later to do something better, even without wiktionary. For instance, it might be possible to have a name property (type: string), and add a "named after" qualifier to it. --Zolo (talk) 19:58, 4 March 2013 (UTC)
- English: Another problem (quite similar is about the story of town's names for exemple : (2046) Leningrad. Otourly (talk) 20:11, 7 March 2013 (UTC)
- English: Definitely. Another very good example. For now, only signifieds have items; maybe signifiers should have items as well (cf. en:Signifier). Touriste could be right. The wiktionary import in wikidata could allow this one day.
- Français : Tout à fait, voilà encore un excellent exemple des problèmes que peut soulever cette propriété. Pour le moment, seuls les signifiés ont un élément associé ; peut-être que les signifiants devraient également en avoir un (cf. fr:Signifié et signifiant). Touriste a probablement raison, ce serait la manière la plus propre d'utiliser cette propriété : <signifié> nommé en référence à <signifiant>. Toutefois, importer tous les wiktionnaires, si c'est juste pour cette propriété, ça tient un peu de l'overkill. Il y a toutefois fort à parier qu'on tire bien d'autres avantage d'un tel import.
- --Gloumouth1 (talk) 21:02, 7 March 2013 (UTC)
- English: Another problem (quite similar is about the story of town's names for exemple : (2046) Leningrad. Otourly (talk) 20:11, 7 March 2013 (UTC)
- English: Yes, that would probably be a good idea to say "one of the name in one of the languages", because we currently have Big Ben is named after Elizabeth II, which sounds weird in all languages. Actually, Big Ben was officially renamed Elizabeth Tower after Elizabeth II. Any idea for a concise label ? --Zolo (talk) 19:51, 4 March 2013 (UTC) Or maybe, it will be possible later to do something better, even without wiktionary. For instance, it might be possible to have a name property (type: string), and add a "named after" qualifier to it. --Zolo (talk) 19:58, 4 March 2013 (UTC)
- English: another example, Q1054240, named after Alain Aspect only in French.
- Français : un autre exemple sympa, Q1054240, que les Français semblent les seuls à avoir nommé en référence à Alain Aspect.
- --Gloumouth1 (talk) 12:56, 25 March 2013 (UTC)
- I also agree that this property should be used at the root level of an element, but only as a qualifier for the (translatable) name of the element itself.
- Unfortunately, there's no interface to add qualifiers to names shown the list of translations at top of the page of an element.
- This would require some addition there, so that we deprecate its use as a basic property (not even with a language qualifier to restrict it), and only allow it as a qualifier for the basic name property (whose language is explicit and mandatorily present).
- Note that even when it will be used as a qualifier for a translated name (in an explicit language), the referenced element may explicitly give a different language (useful to qualify exonyms which are created in a _target language with a name whose origin is the name of an origin object as it was in the origin language, but not necessarily the current name of that origin object in the current language), so two qualifiers would be needed under a translated name : "named in referenced to" (P138) and "language"; possibly also a "date" or "period" qualifier when this name was used in that language. Verdy p (talk) 15:37, 23 February 2016 (UTC)
Sondage // Survey
edit@Otourly, Gloumouth1, Eric-92, Touriste, whym, Zolo: @Verdy p, FischX, Infovarius, VIGNERON:
Français suite à la discussion ci-dessus, je vous propose un sondage afin d'arriver à un consensus sur la manière de gérer les différences entre langues. Le sondage n'est pas encore lancé et je vous ai notifié afin que vous commentiez/améliorez la proposition ci-dessous. Pamputt (talk) 09:52, 14 May 2016 (UTC)
English following the discussions above, I propose a survey in order to find a consensus on how to manage the language differences. The survey is not yet started and I notified you so that you can comment/improve the proposition I did below.
Doit-on utiliser un qualificateur avec la propriété named after (P138) ? / Must we use a qualifier with the property named after (P138)?
editOui/Yes
editNon/No
editNeutre/Neutral
editSi oui, quelle propriété doit-on utiliser ? / If so, which property should we use?
editAutre/Other
editEntre l'élément de départ et celui d'arrivée, auquel s'applique la langue spécifiée ? / Among first and last items, on which one does the specified language is applied?
editFrançais : lorsque la langue est spécifiée, à quel élément s'applique-t-elle ?
l'élément A ou l'élément B ? Par exemple, en allemand, on a
ce qui donne « Bleistift » named after (P138) « Blei » ; la langue s'applique donc aussi bien à l'élément de départ (élément A) qu'à l'élément d'arrivée (élément B). Autre exemple,
ce qui donne « Ares Vallis » named after (P138) « Άρης, Áris » en grec (et Mars pour la plupart des autres langues). La langue s'applique donc à l'élément d'arrivée (élément B) tandis que l'élément A se nomme ainsi dans la majorité des langues. Un dernier exemple avec nonius (Q192772) (cliquez pour voir).
Anglais : when a language is used as a qualifier, to which item is it applied?
Items A or B? For example, in German, there is
that gives « Bleistift » named after (P138) « Blei » ; language is valid both for first item (item A) and last item (item B). Another example,
that gives « Ares Vallis » named after (P138) « Άρης, Áris » in Greek (and Mars in most of the other languages). Language is than applied to the last item (item B) whereas item A is named like this in most of the languages. A last example with nonius (Q192772) (click on it).
Élément de départ
editÉlément d'arrivée
editAutres
editNamesake
editThis property should work fine with ships' namesakes. But, probably shouldn't be used for every namesake scenario. So, only use if a namesake can be found within a reliable source. Danrok (talk) 15:24, 20 May 2013 (UTC)
- What's the argument against other namesake scenaria? Arlo Barnes (talk) 19:55, 27 October 2019 (UTC)
- Does P138 have an inverse property? It doesn't seem to. Jerimee (talk) 23:18, 9 December 2024 (UTC)
Historical names
editHow to handle items that have had several names durig its liftetime? For example Q1531757 (Globen/Isstadion/Slakthuset metro station)? /Esquilo (talk) 18:51, 26 January 2014 (UTC)
- Qualifiers: start time, end time --Chris.urs-o (talk) 07:28, 11 January 2015 (UTC)
- Also, use the "applies to name" qualifier to help distinguish. Arlo Barnes (talk) 19:55, 27 October 2019 (UTC)
Update on use guidelines ?
editAs discussed above, an issue with this proerty is that we do not always not for sure which name it refers to. We now have monolongual-text datatype. Maybe it would make sense to use this property as a qualifier for properties like official name (P1448). For easier data retrieval, we could also make it work both ways (use p528 as a qualifier for name + name as a qualifier of P528), but I think it would be a bit cumbersome. --Zolo (talk) 16:26, 2 September 2014 (UTC)
Interlanguage problem
editFor example pencil (Q14674) is in German named after lead (Q708) this is different in other languages, how can we handle this issue? --FischX (talk) 00:11, 14 March 2015 (UTC)
- One should put qualifier to the statement (with language of work or name (P407), for example). --Infovarius (talk) 21:42, 18 March 2015 (UTC)
- HI FischX and Infovarius Should we use language of work or name (P407) or P2439 (P2439)? I naturally used P2439 (P2439) on Ares Vallis (Q784395) (and coming here *afterward* to ask how I should handle it, sorry, my bad). Cdlt, VIGNERON (talk) 16:07, 12 March 2016 (UTC)
- Honestly, I don't know: I don't see a difference between these two properties. --Infovarius (talk) 22:14, 23 July 2016 (UTC)
- HI FischX and Infovarius Should we use language of work or name (P407) or P2439 (P2439)? I naturally used P2439 (P2439) on Ares Vallis (Q784395) (and coming here *afterward* to ask how I should handle it, sorry, my bad). Cdlt, VIGNERON (talk) 16:07, 12 March 2016 (UTC)
Recently, a contraint was added to prevent that this was used with Wikimedia list article (Q13406463). As there is no discussion about it and not really a reason why we can't indicate how a given list was named, I removed the constraint. --- Jura 04:56, 15 August 2015 (UTC)
Reverse property
editFor reason that statement 'entity or event that inspired the subject's name, or namesake' is reversible 'subject's name was inspired to name such entity, the subject's name is namesake for ' we need to create reverse property. This will be used, e.g., for defining subject related toponyms.Avatar6 (talk) 12:36, 13 November 2015 (UTC)
Support, - Kareyac (talk) 08:59, 28 February 2016 (UTC)
- For a discussion of this in 2014/2015, see Wikidata:Property_proposal/Archive/28#it_gave_its_name_to.
--- Jura 09:07, 28 February 2016 (UTC)
word subclasses
edit- 'Subclass' should be an approved qualifier. Wikipedia titles are nouns. An item could be named after an adverb, adjetive, verb etc. --Chris.urs-o (talk) 11:07, 23 July 2016 (UTC)
How to model the relationship to the name-giving lexeme?
editNow that we have lexemes and forms, I think it should be possible somehow to express that Euplocania equorum (Q55541192) is named after equorum (L6830-F8) rather than Equus (Q27022). How could we go about that? --Daniel Mietchen (talk) 23:56, 14 July 2018 (UTC)
- I came here with the same question. I wanted to model that Heroku (Q2350702)named after (P138)heroic (L269673)+Heroku (Q2350702)named after (P138)haiku (Q37707) and wasn't able to do so because the property doesn't support this.
- Building off of how the constraints of subject lexeme (P6254) are modeled, I would suggest adding subject type constraint (Q21503250)=lexeme (Q111352) (more specifically, property constraint (P2302)subject type constraint (Q21503250)
class (P2308)lexeme (Q111352) relation (P2309)instance or subclass of (Q30208840)), and possibly also subject type constraint (Q21503250)=entity (Q35120) (more specifically property constraint (P2302)subject type constraint (Q21503250) class (P2308)entity (Q35120) relation (P2309)instance or subclass of (Q30208840)) to this property. Would this be sufficient to support lexemes as values? Waldyrious (talk) 20:27, 12 November 2022 (UTC)
OSM tags
editI came here to add them, but now that I see they are already there, it strikes me it might not be quite the right place to put them, since the property is an "instance of | Wikidata property to indicate a name", which is not true for the tags since they are not Wikidata properties. Or is "OSM tag or key" allowed to apply to merely related concepts? Arlo Barnes (talk) 03:53, 24 October 2018 (UTC)
- Hey, past me. I would say that while this is indeed a Wikidata property, it is also just a property more generically, same as the OSM tags. Arlo Barnes (talk) 19:53, 27 October 2019 (UTC)
allowed qualifiers constraint: type of kinship
editWould it be OK to add "kinship to subject (P1039)" to the "allowed qualifiers constraint (Q21510851)"? Like Joseph Jefferson (Q3185137) is maternal grandfather (Q4994791) to Joseph Jefferson Farjeon (Q3810223) 1Veertje (talk) 20:28, 26 July 2019 (UTC)
- Why duplicate that you already can get from the father/mother statements?
- You can add named after (P138) as qualifier to Q3810223#P735. I don't think Q3810223#P138 is a good idea. --- Jura 18:24, 30 October 2019 (UTC)
Mandatory qualifier applies to name of subject (P5168)
editI removed that as I'm not sure why it should be added systematically and related questions at Property talk:P5168 remain unanswered. --- Jura 11:00, 23 June 2020 (UTC)
Use of applies to name of subject (P5168) and applies to name of object (P8338) qualifiers
editPlease see Property_talk:P8338#Use_on_Q6556889#P138 (about "Sons" in (e.g.) "xyz & Sons" and "I" in "How I met your mother"). --- Jura 11:45, 23 June 2020 (UTC)
Value constraint?
editShould there be some restriction of what an item can be named after? Events, places, persons and "other entities" are mentioned in the descriptions, while only places, persons and divine/mythical beings appear in the property examples, thus all of them supposedly having proper names that can be made into words (or new names).
But then I find geographic location (Q2221906) being named after (P138) locus (Q12885571) and relative location (Q23008351), and I'm concerned we may be incubating a djungle of etymology statements where almost any single item may call for anything between one and 300 instances of named after (P138). Isn't this area best left for the lexeme database to deal with (I haven't been there yet, so I don't know how it's doing)?
Should I ping someone, or do I just leave my question here for any interested bystander to attend to? --SM5POR (talk) 17:34, 2 July 2020 (UTC)
I agree with SM5POR both in terms of the substance of their post, as well as being afraid to touch anything here. The next such person coming along should feel empowered and boldly make a change. --Matthias Winkelmann (talk) 12:25, 3 September 2020 (UTC)
Label name change in Spanish
editThe property used to have an erronous label, it was "nombrado por" (which means "named by") and I've changed it to "lleva el nombre de", this second expression is a little bit more usual and can apply to both objects and people, although I am open to suggestions. Let me know what you think Silva Selva (talk) 12:07, 9 November 2022 (UTC)