Property talk:P1366

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

replaced by
other person or item which continues the item by replacing it in its role. Use P156 ("followed by") if the item is not replaced nor identical, but adds to the series (e.g. books in a series).

Description	"is succeeded by", e.g. for sequences of entities where the next one replaced the previous one: political offices, hereditary titles, states and administrative entities...
Represents	replacing entity (Q45025415)
Data type	Item
Domain	generic (note: this should be moved to the property statements)
Allowed values	item of the same nature (note: this should be moved to the property statements)
Usage notes	For sequences of entities where the next one replaced the previous one: political offices, hereditary titles, states and administrative entities... Use in combination with replaces (P1365). For buildings, rather use structure replaces (P1398). Can be used as qualifier on a statement describing a sequence. If item is last in a series, value type for this property should be "no value", rather than a value of "last" (Q30013662),, which is ambiguous. (English)
Example	According to this template: George W. Bush (Q207)position held (P39)President of the United States (Q11696)replaced by (P1366)Barack Obama (Q76) According to statements in the property: Ptolemy XII Auletes (Q39991) → Cleopatra (Q635) Cleopatra (Q635) → not applicable Canada East (Q2935756) → Quebec (Q176) George W. Bush (Q207) → Barack Obama (Q76) When possible, data should only be stored as statements
Robot and gadget jobs	DeltaBot does the following jobs: Move source to qualifier
Tracking: usage	Category:Pages using Wikidata property P1366 (Q61244561)
See also	structure replaced by (P167), followed by (P156), gave up territory to (P7904), structure replaces (P1398)
Lists	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/Complex constraint violations/P1366 Database reports/Constraint violations/P1366
Proposal discussion	Proposal discussion
Current uses	Total 329,245 Main statement 108,291 32.9% of uses Qualifier 220,856 67.1% of uses Reference 98 <0.1% of uses
Search for values

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

Inverse property of “replaces (P1365)”:
if [item A] has this property (replaced by (P1366)) linked to [item B],
then [item B] should also have property “replaces (P1365)” 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/P1366#inverse, SPARQL

Qualifiers “point in time (P585), applies to part (P518), has cause (P828), reason for deprecated rank (P2241), reason for preferred rank (P7452), approved by (P790), valid in place (P3005), statement is subject of (P805), nature of statement (P5102), has characteristic (P1552), excluding (P1011), sourcing circumstances (P1480), together with (P1706), object has role (P3831), subject named as (P1810), consequence of text (P9680), applies to name of subject (P5168), section, verse, paragraph, or clause (P958), applies to jurisdiction (P1001), country (P17)”: 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).
List of violations of this constraint: Database reports/Constraint violations/P1366#allowed qualifiers, SPARQL

Scope is as qualifier (Q54828449), as main value (Q54828448): 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/P1366#Scope, 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/P1366#Entity types

Conflicts with “structure replaced by (P167)”: 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/P1366#Conflicts with P167, search, SPARQL

None of N/A (Q929804), last (Q30013662): value must not be any of the specified items.
Replacement property:
Replacement values: (Help)

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

Value "last" not allowed
If item is last in a series, value type should be "no value", rather than a value of last (Q30013662), which is ambiguous (Help)
Violations query: SELECT ?item ?itemLabel WHERE {?item ?prop [pq:P1366 wd:Q30013662].}
List of this constraint violations: Database reports/Complex constraint violations/P1366#Value "last" not allowed

This property is being used by: cs:Šablona:Infobox - osoba, cs:Šablona:Infobox - panovník, cs:Šablona:Infobox - politická funkce, cs:Šablona:Infobox - webová stránka be:Шаблон:Орган выканаўчай улады el:Πρότυπο:Κουτί πληροφοριών ποδοσφαιρικής διοργάνωσης, el:Πρότυπο:Γεωγραφική οντότητα n:fr:Modèle:Topic cat hu:Sablon:Cég infobox, hu:Sablon:Egyházmegye infobox, hu:Sablon:Vasúti jármű infobox, hu:Sablon:Vezető infobox, hu:Sablon:Sablonhomokozó, hu:Sablon:Szervezet infobox, hu:Sablon:TV-csatorna infobox, hu:Sablon:Számítógép infobox, hu:Sablon:Kormány infobox, hu:Sablon:Weboldal infobox, hu:Sablon:Metró infobox hy:Կաղապար:Տեղեկաքարտ Հատուկ ծառայություն, hy:Կաղապար:Տեղեկաքարտ Հեռուստաալիք, hy:Կաղապար:Տեղեկաքարտ Ֆայլի ֆորմատ, hy:Կաղապար:Տեղեկաքարտ Օրենսդրական ակտ, hy:Կաղապար:Տեղեկաքարտ Կրոն uk:Шаблон:Орган виконавчої влади, uk:Шаблон:Телевізійний канал, uk:Шаблон:Видавництво, uk:Шаблон:Орган виконавчої влади/пісочниця es:Plantilla:Ficha de banco central, es:Plantilla:Ficha de software, es:Plantilla:Ficha de gobierno, es:Plantilla:Ficha de conector ca:Plantilla:Infotaula d'organització, ca:Plantilla:Infotaula eina ru:Шаблон:Административная единица Российской империи ce:Кеп:Российн империн дминистративн дакъа, ce:Кеп:Российн империн административан дакъа ro:Format:Infocaseta Parlament cv:Шаблон:Раççей империн администрациллĕ виçи ast:Plantía:Ficha de bancu central, ast:Plantía:Moneda, ast:Plantía:País/cabecera estáu desapaecíu be-x-old:Шаблён:Тэлескоп, be-x-old:Шаблён:Валюта he:תבנית:מטבע nn:Mal:Infoboks verksemd, nn:Mal:Infoboks operativsystem diq:Şablon:Kayker, diq:Şablon:Merdumi, diq:Şablon:Merdumî, diq:Şablon:Nuştekar, diq:Şablon:Kes pnb:سانچہ:ص.م/قبل-بعد ويكي بيانات az:Şablon:Rusiya İmperiyasının inzibati vahidi, az:Şablon:Hökumət en:Template:Infobox video game engine inh:Ло:Административная единица Российской империи ang:Bysen:Cyþþubox Æþel fr:Modèle:Infobox Compagnie ferroviaire vec:Modeło:Infobox de Goerno, vec:Modeło:Infobox de Stato, vec:Modeło:Infobox de Zeografia pułìtega, vec:Modeło:Infobox de Zeografia pułìtega/proa zh:Template:Infobox constituency, zh:Template:Infobox Electoral districts in Hong Kong lij:Template:Biografîa zh-yue:Template:維基數據行星明細, zh-yue:Template:維基數據君主明細, zh-yue:Template:Infobox constituency sv:Mall:Faktamall företag commons:Template:Wikidata Infobox/core d:Template:Wikidata Infobox/core s:ban:Mal:Wikidata Infobox/core ban:Mal:Wikidata Infobox/core mr:साचा:विकिडेटा माहितीचौकट/core lv:Veidne:Wikidata Infobox/core it:Template:Organo governativo eo:Ŝablono:Informkesto organizaĵo, eo:Ŝablono:Informkesto registaro, eo:Ŝablono:Informkesto firmao, eo:Ŝablono:Informkesto skribo, eo:Ŝablono:Informkesto organizaĵo/dokumentado scn:Template:Organo governativo be-tarask:Шаблён:Валюта, be-tarask:Шаблён:Тэлескоп, be-tarask:Шаблён:Дзяржаўная ўстанова yue:Template:Infobox constituency, yue:Template:維基數據君主明細, yue:Template:維基數據行星明細 pt:Predefinição:Info/Software/Wikidata Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Qualifier?

When should this property be used as qualifier and when not? E.g. when an item is about a village and former municipality, I think this property must be used as qualifier with the 'is a' municipality claim. When the item is only about a former municipality this is not needed. Or for clearity, should we always use this property as qualifier? Michiel1972 (talk) 09:36, 4 July 2014 (UTC)

english translation: replacement of succeeds/italian translation: replacement of succeduto a

Moved from Property talk:P1365. --Yair rand (talk) 02:27, 25 February 2016 (UTC)

1.replaces/substitutes/supersedes/supercedes/surrogates/displaces/takes the place of succeeds, because succeeds also means follow, so it is no clear difference to follows (P155)
a very important parameter is, that follows (P155)/ followed by (P156) only apply with identical items, or when the item is included. E.G. If city A, B, and C are replaced by (P1366) City D; City D replaces (P1365) and is (followed by (P156)) of City A-C, but each of Cities A, B, C is not follows (P155) of City D. See Milwaukee (Q37836) replaces (P1365) Juneautown (Q15242198), Kilbourntown (Q15242201), Walker’s Point (Q15242213); Juneautown (Q15242198), Kilbourntown (Q15242201), Walker’s Point (Q15242213) are replaced by (P1366) Milwaukee (Q37836). Should be used with dissolved, abolished or demolished date (P576) instead of end time (P582)--Oursana (talk) 12:01, 28 October 2014 (UTC)

2. it: same with sostituito da consistent with structure replaced by (P167)--Oursana (talk) 12:01, 28 October 2014 (UTC)

"Valid in place" as qualifier

I'd like to add valid in place (P3005) as a valid qualifier when one item replaces another in a specific place. Any objections? - PKM (talk) 21:28, 27 August 2019 (UTC)

 Done. @PKM: I agree with you and have added P3005 (valid in place) as an allowed qualifier. Thank you. --Neo-Jay (talk) 10:23, 14 July 2020 (UTC)

qualifier: sourcing circumstances

Curious the constraint issue for sourcing circumstances (P1480) of Shang dynasty (Q128938). The qualifier is invalid when used in replaced by (P1366) and point in time (P585)? Thank you for your help.jshieh (talk) 14:13, 23 February 2021 (UTC)

"Ordered by" as qualifier

IMHO it would make sense to use the ordered by (P8004) qualifier with this property. Is it OK to just add it or should I request it and and let proper people handle it? Tengwar (talk) 23:10, 9 May 2021 (UTC)

Using the property when the item is not dissolved

Should this property be used when the item is not ending it's functionality? To be more specific, can it be used as a "reverse property" for separated from (P807)? Yger reverted my change for the municipality Botkyrka Municipality (Q113718) where only a small part was broken out to form Salem Municipality (Q516080) but the former is still existing to this very day. Hence I argue that the municipality have not been replaced in a semantic meaning, but that only the administrative borders have changed. This seems to be a novel use and we do for example not see that

⟨ Virginia (Q1370)    ⟩ replaced by (P1366) ⟨ West Virginia (Q1371)    ⟩

So the question is, can the property be used when the item itself has not stopped with its services, but only the borders of that item changed? Ainali (talk) 09:43, 15 August 2021 (UTC)

In these cases I use applies to part (P518) to specify it is not the whole entity that is dissolved.Yger (talk) 10:04, 15 August 2021 (UTC)

Probably the property gave up territory to (P7904) is more what you are looking for? Ainali (talk) 12:28, 15 August 2021 (UTC)

For some of the cases, like when some islands are transferred from one existing adm unit to another existing unit, the pair gave up territory to (P7904) and gained territory from (P7903) would work fine and much better than replaced by (P1366) replaces (P1365) I have used. The majority of cases, though, is of an adm unit that have been merged and then recreated as a "new" adm unit. Here separated from (P807) correctly is proposed to be used for the recreated unit. But what to use for the unit where the area is broken out, when there does not exist any property corresponding to separated from (P807)? gave up territory to (P7904) with applies to part (P518) looks for me more confusing than replaced by (P1366) with applies to part (P518) and the latter is what I have use for some 1000 WD objects.Yger (talk) 13:33, 15 August 2021 (UTC)

Why is it more confusing? It's literally what happened. They "gave up territory to" a new administrative unit. They were not "replaced", since they still exist. So P1366 is a lot more confusing from a semantic point of view, since replacing carries the meaning that the original is ceasing to do something, but in your examples, they are instead continuing to be municipalities and filling all of these functions, only to a slightly reduced area. Ainali (talk) 13:53, 15 August 2021 (UTC)

The main problem is that an inverse of separated from (P807) is missing which forces an asymmetrical solution. In the examples it is not about a slightly replaced area but that the area is split in more or less half, and that the lostpart are is an old established adm unit that is being recreated. To use significant event (P793) and boundary change (Q28953942) asymmetrical is for med more confusing then replaced by (P1366). How can if be a boundary change (Q28953942) on one unit and not the other? But both solutions can be critized and is boils down to "Tycke och smak".Yger (talk) 08:00, 16 August 2021 (UTC)

We have plenty of asymmetrical properties. In fact, there are some that even argue that we should have no symmetrical ones, since it is duplication of data that could easily be inferred, so that is no good reason to bend other properties backwards to try to make them fit a symmetrical use. Ainali (talk) 09:17, 16 August 2021 (UTC)

Is there a particular need/use case for a symmetrical solution in this case? Otherwise, I'm in favor using only separated from (P807). Abbe98 (talk) 19:53, 18 August 2021 (UTC)

There is a definitive need to express in the infobox and WD object of the commune that is losing that a major part has gone, making the commune before and after different communes. Look at Vaxholm Municipality (Q500090) who "lost" 87% of its area in 1983. Yger (talk) 06:20, 20 August 2021 (UTC)

If they are truly different, "replaced by" is correct, and the municipality should have dissolved, abolished or demolished date (P576) and the new municipality should be a new item. If not, they are not different at all, which we also can see since they have the same Swedish Organization Number (P6460), that is, they are the same legal entity before and after some area (however large it may have been) was given away to form a new municipality. Ainali (talk) 08:05, 22 August 2021 (UTC)

It's currently not in the infobox on sv.wp as far as I can see and if one would add it in the future wouldn't a asymmetrical property be god enough? Abbe98 (talk) 12:05, 27 August 2021 (UTC)

@Yger any thoughts regarding the above? Abbe98 (talk) 14:07, 12 November 2021 (UTC)

in several cases (mostly regarding församling) I have created a separate object after the split A->_B and A' as A and A' in many aspects are different even if they have the same name.Yger (talk) 14:54, 12 November 2021 (UTC)

I see now that Ainali has made changes and replaced Ersätter med utbrutit for what I understand all communes that were split after 1974. As the template was adjusted it looks ok in viewing the article. These things are intellectually complicated, and I as fully aware and content with what I did a few years ago. But my brain is getting slower, so I have harder arguing when we are not able to sit down and look through the many variants of this merge and dissolve cases. I am still of the opinion that my use are and were correct but leave it for now.Yger (talk) 15:22, 12 November 2021 (UTC)

Using the property when the item never existed

Should we use the property when the replaced item is a project which has been cancelled, and is replaced by an item which actually exist ? (For instance, a cancelled airport project, whose function is replaced by refitting an actual airport ?) --Chaoborus (talk) 17:44, 5 October 2021 (UTC)

Conflicts with 'structure replaced by' (P167)?

I was editing Stargel Stadium (Q117460496) and noticed that a constraint violation popped up because I used both replaced by (P1366) and structure replaced by (P167). I had good reason for doing this. When Stargel Stadium (Q117460496) (a small high school football stadium) was torn down in 2018, it was to make way for TQL Stadium (Q54465634) (a large professional soccer stadium). Meanwhile, a new high school stadium of the same name was rebuilt across the street as Stargel Stadium (Q117460472). So I have added these two statements:

1. Stargel Stadium (Q117460496)structure replaced by (P167)TQL Stadium (Q54465634), because TQL Stadium now occupies the geographic location of old Stargel Stadium (well actually, TQL Stadium's footprint is larger than the footprint of old Stargel Stadium – they also bought and torn down some neighboring buildings to make way for it)
2. Stargel Stadium (Q117460496)replaced by (P1366)Stargel Stadium (Q117460472), because new Stargel Stadium replaces the role of the old Stargel Stadium

Is my usage incorrect, or is the constraint wrong in this case? –IagoQnsi (talk) 01:48, 7 April 2023 (UTC)

I went ahead and changed the constraint to be a suggestion constraint. I think it makes sense to pop up the suggestion to make sure editors are paying attention to the difference between the two properties, but it's not a constraint that should be enforced. –IagoQnsi (talk) 17:27, 10 March 2024 (UTC)