Open main menu

Property talk:P793

Documentation

significant event
significant or notable events associated with the subject
Descriptionsignificant events associated with the subject. Use only when no more specific date property exists. See the list of proposed significant events.
Representskey event (Q2245405)
Data typeItem
Domain
According to this template: all domains
According to statements in the property:
entity (Q35120)
When possible, data should only be stored as statements
Allowed valuesoccurrence (Q1190554) (occurrence) or event (Q1656682) (organized meeting) (note: this should be moved to the property statements)
Usage notesMust be qualified with appropriate date and context properties.
ExampleDennewitz (Q882375)Battle of Dennewitz (Q647827)
Friedland (Q4492725)ceremonial ship launching (Q596643)
Vladimir Putin (Q7747)First inauguration of Vladimir Putin (Q24957710)
Tracking: usageCategory:Pages using Wikidata property P793 (Q20990058)
See alsosignificant person (P3342), commissioned by (P88), owned by (P127), closest approach (P6354), feast day (P841), significant place (P7153)
Lists
Proposal discussionProposal discussion
Current uses81,487
Search for values
Value type “occurrence (Q1190554), fictional event (Q14136353), mythical event (Q24336466), temporal entity (Q26907166): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value occurrence (Q1190554), fictional event (Q14136353), mythical event (Q24336466), temporal entity (Q26907166) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P793#Value type Q1190554, Q14136353, Q24336466, Q26907166, SPARQL, SPARQL (new)
None of discovery (Q753297), retirement (Q946865): value must not be any of the specified items. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P793#none of, SPARQL, SPARQL (new)
None of foundation (Q157031): value must not be any of the specified items. (Help)
List of this constraint violations: Database reports/Constraint violations/P793#none of, hourly updated report, SPARQL, SPARQL (new)
Type “entity (Q35120): element must contain property “instance of (P31)” with classes “entity (Q35120)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P793#type Q35120, SPARQL, SPARQL (new)

External useEdit

This property is being used by:

fr:Modèle:Date clé


Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

How do we use this property?Edit

This property can be used to create a timeline of key events associated with an item so it can be used for any item that has a lifetime sequence that might be expressed as a timeline.

  • Use this property for events associated with one-off objects, like ships, buildings, works of art, motorways, railway lines, dams, and other large construction projects. Values such as Contract, Keel laying, Foundation, Topping out, Launch, completion, renovation, damage, closure, destruction.
  • Use this property for events associated with mass produced objects like cars, mobile phones, airplanes, software, video games. Values such as prototype, initial sale, design change, final sale, end of support.
  • Use this for books (literary works), movies, albums which are works of art but with multiple examplars. Values such as Recording, publication, Premiere, Golden discs, etc.
  • Use this property for a scientific or academic or political theory or paradigm - heliocentrism, evolution, expanding universe, salvation by faith alone, abolition of slavery, legalisation of homosexuality, prohibition of alcohol, Tea party movement. Values such as first publication, conferences held, laws passed, nobel prize won.
  • Use this property for organisations. Values such as foundation, milestones (a thousand members, a million members, turnover reaches a million dollars etc.), new branches, new product areas, new headquarters building, bankruptcy, takeover.
  • Use this property for clothing items, fads, or fashion trends with value "heyday" to indicate the subject's period of peak popularity or influence when that differs from its first appearance (inception).

This property links to items. These may be generic items for a class of events. These items should have the statement subclass of (P279)=key event (Q2245405) or subclasses of this such as key event (ships) (Q14904124).

Alternatively this property can be used to link to items for specific events related to the subject, as a way of linking these items in a chronological sequence or geographical extent.

Domain Event class Qualifier (time) Qualifier (location) comment
Company/commune/country change of ownership (Q14903979) point in time (P585)
name change (Q2343619) point in time (P585)
corporate spin-off (Q1186164) point in time (P585)
merge (Q17853087) point in time (P585)
Person amputation (Q477415) point in time (P585)
Creative work première (Q204854)
Building/infrastructure/monument groundbreaking (Q1068633) point in time (P585)
cornerstone laying ceremony (Q18752057) point in time (P585)
construction (Q385378) start time (P580), end time (P582)
topping out (Q1075723) point in time (P585)
inauguration (Q1417098) and/or dedication (Q1762010) and/or consecration (Q125375) point in time (P585)
opening (Q15051339) point in time (P585)
renovation (Q2144402) start time (P580), end time (P582)
closure (Q5135520) point in time (P585) or start time (P580), end time (P582) start time (P580), end time (P582) if the demolition is over a period, point in time (P585) if the demolition is done in one day
demolition (Q331483) point in time (P585)
reopening (Q16571590) point in time (P585)
relocation (Q2918584) point in time (P585)
destruction (Q17781833) point in time (P585) cause of destruction (P770) this qualifier is important for accidental destruction not for planned demolition.
service entry (Q29933828) point in time (P585)
service retirement (Q29933838) point in time (P585)
Car/plane/Computer/item
Example: Opel Senator (Q964775)
presentation (Q604733) point in time (P585) location (P276)
production (Q739302) start time (P580), end time (P582) see Production or distribution ?
Ship
Example: CSS Rappahannock (Q2932019)
order (Q566889) point in time (P585)
keel laying (Q14592615) point in time (P585)
ceremonial ship launching (Q596643) point in time (P585)
shipbuilding (Q474200) end time (P582)
maiden voyage (Q1501837) point in time (P585)
ship commissioning (Q14475832) point in time (P585)
ship reclassification (Q21725151) point in time (P585)
ship decommissioning (Q7497952) point in time (P585) location (P276)
destruction (Q17781833) start time (P580), end time (P582) location (P276) cause of destruction (P770) is important for accidental destruction, not for planned demolition.
shipwrecking (Q906512) point in time (P585) location (P276)
retirement (Q946865) point in time (P585) location (P276)
ship disposal (Q7497950) point in time (P585)
scuttling (Q1786766) point in time (P585)
ship breaking (Q336332) start time (P580), end time (P582) location (P276)
Law adoption (Q2424916) point in time (P585)
coming into force (Q490812) point in time (P585)
promulgation (Q446780) or Royal Assent (Q1070654) point in time (P585)
Clothing/fad/fashion trend or similar heyday (Q47468023) point in time (P585) or start time (P580), end time (P582) start time (P580), end time (P582) if source gives start/end dates, point in time (P585) if the source indicates a period as "1950s" or "18th century"
Artworks like painting (Q3305213), visual artwork (Q4502142), sculpture (Q860861), drawing (Q93184), painting (Q3305213) acquisition (Q22340494), bequest (Q211557), gift (Q707482), sales (Q194189), auction (Q177923), donation (Q1124860), demolition (Q331483), art theft (Q1756454), destruction (Q17781833), conservation (Q217102), date of unveiling (Q16717192), discovery (Q753297) point in time (P585) Most of those properties should specify different roles of people involved:
  • old owner and new owner in case sales, auctions and acquisitions
  • identity of the thief, or person who discovered, destroyed, demolished or did conservation work

As of March 2018, property "of (P642)" seems to be used to specify people involved, which makes little sense, at least in English.

Inventions patent application (Q57206193) point in time (P585)

Preferred alternate specialized propertiesEdit

DiscussionEdit

We need an explanation about how to use this property and in which field we can apply this. Snipre (talk) 08:14, 18 August 2013 (UTC)

I have added a first draft of the explanation above. Filceolaire (talk) 11:01, 18 August 2013 (UTC)
I propose to use start time (P580) instead of point in time (P585) in order to keep the data extraction process as simple as possible: this allows the extraction of events which last more than one day. By convention if the event lasts only one day the end date can be omitted. Snipre (talk) 09:01, 18 August 2013 (UTC)
I disagree. Start date' with no 'end date' usually means the item is still ongoing. I think we should use 'Point in time' for events that happen at one time. When someone does a graphical timeline they will want different symbols anyway (star for one off; bar for event with duration) so the data needs to make it clear which is which. Filceolaire (talk) 11:21, 18 August 2013 (UTC)
Actually, "point in time" doesn't make sense. The DateType, based at least on the data that it spits out, will handle down to the second level (and likely lower?). There is very rarely a "key event" which lasts for only one second. --Izno (talk) 22:21, 20 August 2013 (UTC)
It can also be as vague as just the year. When they have sorted the user interface it should be possible to just specify the century, the millenium or any uncertainty we want to specify. Filceolaire (talk) 23:18, 20 August 2013 (UTC)

Production or distribution ?Edit

Use production (Q739302) or distribution (Q867147) ?

(*) But i think distribution (Q867147) is more correct ! LucaBiondi (talk) 12:28, 24 August 2013 (UTC)

Heu, production is linked with distribution: you can't distribute if you don't produce and the small due to stocks is never considered. For software we can discuss about the use of production: we can use operation in that case. But at the end we really need an unique term for all items because each field use a specific term we won't be able to extract the information in wikipedia. Snipre (talk) 12:54, 24 August 2013 (UTC)
I agree with you, we need an unique term. I'll use production (Q739302) but in the case of the cars the meaning is the date of the start or the end of the marketing. LucaBiondi (talk) 17:39, 24 August 2013 (UTC).


More clarifications on rulesEdit

Following these rules, the key events e.g. for World Trade Center (Q11235) currently are only half-correct. Some follow these rules, e.g. groundbreaking (Q1068633), while September 11 attacks (Q10806) should be changed so it uses cause of destruction (P770), and for something like World Trade Center bombing 1993 (Q11240) there would be no place at all, even though this event is closely linked to the building. More generally, it's hard to link a specific item if we have one (e.g. there are several Wikipedia article about the construction of building X, but how to link it here?). And e.g. if we would allow a value nuclear and radiation accident (Q1620824), how to link Fukushima nuclear accident (Q171178) to Fukushima Daiichi Nuclear Power Plant (Q114295) (currently done using a statement is subject of (P805) qualifier, which looks a bit unnatural to me)? --YMS (talk) 10:26, 3 January 2014 (UTC)

1. the way Fukushima Daiichi Nuclear Power Plant (Q114295) links to Fukushima nuclear accident (Q171178) is, I believe, the right way to go:
Fukushima Daiichi Nuclear Power Plant (Q114295) : significant event (P793) => nuclear and radiation accident (Q1620824)
qualified with point in time (P585) and statement is subject of (P805) => Fukushima nuclear accident (Q171178)
because Fukushima nuclear accident (Q171178) describes the relation between the plant and its nuclear accident, precisely what is specified in P805 property documentation. It is compact and flexible.
2. I am not too enthusiastic about using significant event (P793) for the construction, but it seems it's the most flexible scheme since the construction needs a start date and an end date, so no "construction date" property would do. However, whatever property is used to track the construction event, any number of items detailing the construction of that building can be associated through qualifier statement is subject of (P805) on the same "construction" statement.
3. I agree with @YMS: on World Trade Center (Q11235) : both significant event (P793) World Trade Center bombing 1993 (Q11240) and September 11 attacks (Q10806) should be rather specified as statement is subject of (P805) attached to, say, Q15236208 and suicide attack (Q217327) (or massacre (Q3199915) or building collapse) respectively.
4. Finally the reverse relation (from the event item to the object undergoing to that event) has no clear property. I know that statement is subject of (P805) should not be used for that, but there is no "object" property. depicts (P180) is the best approximation, I believe. Suggestions welcome.
LaddΩ chat ;) 03:13, 19 March 2014 (UTC)
Why not using the Fukushima nuclear accident (Q171178) item for the key event and setting  ? TomT0m (talk) 13:16, 22 March 2014 (UTC)
@TomT0m: It could be done that way too, but people who set up the rules listed above elected to have a list of generic event types, rather than specific event description items. I guess it was necessary to agree on some scheme. (Note that this was before instance of (P31) was widespread.) LaddΩ chat ;) 22:18, 24 March 2014 (UTC)
Maybe we should change that, this imply less complexity for the user. It's a bot work, and it would be a test to know if we can change anything in Wikidata at that point. TomT0m (talk) 10:16, 25 March 2014 (UTC)
I think the framework described by Laddo makes sense. Creating items for all key events for all items does not seem very convenient to me. --Zolo (talk) 14:09, 25 March 2014 (UTC)
depicts (P180) shouldn't be used for that, it has another domain. --Marsupium (talk) 15:03, 18 July 2014 (UTC)

Properties instead of classes of events?Edit

I'm missing point how properties can do something that items cannot. Yes, small events unlikely to have a separate page at Wikipedia, so we have to create item for them.

Quite opposite, we cannot build hierarchies of properties as we can for pyramids of events.

I cannot see reason why narrow properties were picked here. d1g (talk) 15:00, 1 May 2017 (UTC)

Simply to avoid explosion of items: just take the number of persons having an item in WD, then multiply that number by 4 or 5 and see the number of potential new items (for every person you have at least 2 events, the birth and the death). Snipre (talk) 16:02, 1 May 2017 (UTC)
Why do we need more than 4-5 items as values of P793? P793=birth(PQ585=1900);death(PQ585=2000)? d1g (talk) 17:32, 1 May 2017 (UTC)
In P136 we he have "sculptural genre" (Q18783400), "literary genre" (Q223393) and "musical genre" (Q18783400) classes, next link is about exact genre. We don't have links beyond "rock" (Q11399) class, so we can stop at "death" IMO. d1g (talk) 08:45, 2 May 2017 (UTC)

Some geographic events are periodicalEdit

"point in time" is not a reasonable qualifier if they repeat 10-100/year. d1g (talk) 14:52, 30 September 2017 (UTC)

Could you please provide an example? --Pasleim (talk) 18:34, 30 September 2017 (UTC)

Is the "allowed qualifiers" constraint doing any good?Edit

Almost any qualifier could reasonably apply to a P793 statement; what is the value in trying to capture them all? Swpb (talk) 13:30, 28 March 2018 (UTC)

With each property if you expect to use some qualifiers than it is better to have final list so the people writing tools that interpret this data know what to expect. If needed more qualifiers can be added. --Jarekt (talk) 13:56, 28 March 2018 (UTC)

Strange (mis)use of "of (P642)" qualifier within significant event (P793) propertyEdit

Look at Mona Lisa (Q12418) there is a statement there about significant event (P793) art theft (Q1756454) / of (P642) Vincenzo Peruggia (Q361362). I do not think there was theft of Vincenzo Peruggia, it was theft by Vincenzo Peruggia. Different example: according to www.museunacional.cat Portrait of the Girl Rosó Galia (Q23932099) was "Donated by Joan Miró Folguera" to the museum in 1931 that is modeled on Wikidata by Portrait of the Girl Rosó Galia (Q23932099) significant event (P793) gift (Q707482) / of (P642) private collection (Q768717) in 1931. According to this SPARQL query there are 3750 uses of significant event (P793) / of (P642) pairs and I can not find any that make sense (at least in English). How is significant event (P793) supposed to be modeled? Usually change of ownership events like acquisition (Q22340494), bequest (Q211557), gift (Q707482) or sales (Q194189) are modeled with old owner and new owner names, see for example c:Template:ProvenanceEvent, but how do we model that on Wikidata? Do we need to create new qualifiers for that? --Jarekt (talk) 15:25, 21 March 2018 (UTC)

I wrote the above message at Wikidata:Project chat with only Marsupium agreeing. I copied it here in hopes that we can find some sort of fix to the issue. Maybe we need "by", "old owner" and "new owner" qualifiers? --Jarekt (talk) 14:01, 28 March 2018 (UTC)

@Jarekt: I think new properties are indeed the best option. I think the could also be used as statement properties, for example in theft of Mona Lisa (Q61266859). They would be similar to CIDOC-CRM's P22 transferred title to (acquired title through) and P23 transferred title from (surrendered title through). --Marsupium (talk) 21:29, 22 June 2019 (UTC)

Mandatory qualifier constraint necessary?Edit

I saw that one can add this property without giving a date or period of time the event occured. Shouldn't there be a mandatory qualifier constraint (Q21510856) so that either start time (P580) and end time (P582) or point in time (P585) are required qualifiers? I guess the problem with this would be that the mandatory qualifier constraint means that all of the listed qualifiers have to be given but in this case either the first two qualifiers or the last is/are necessary. It seems that there is no "one-of qualifier constraint" available on Wikidata. I haven't followed the project discussions intensively so I don't know wether such a constraint is still planned or not and if yes why it is not (yet) possible. If it is this topic here can be closed.--Leit (talk) 14:20, 30 May 2018 (UTC)

  • Some events used as value already have a date on the item itself, so adding one in a qualifier isn't really needed.
    --- Jura 18:06, 30 May 2018 (UTC)

"Point in time" mandatory?Edit

Please have a look at St. Judas Thaddäus (Heisterbacherrott) (Q15129444). point in time (P585) is not neccessary because the more precise qualifiers start time (P580) and end time (P582) are already given. So why is point in time (P585) now a mandatory qualifier constraint for this property? I guess it should be mandatory to state either a point in time or a time interval (see above) but not both.--Leit (talk) 16:59, 12 February 2019 (UTC)

I changed it myself.--Leit (talk) 20:21, 15 February 2019 (UTC)
Agree! --Marsupium (talk) 18:11, 8 March 2019 (UTC)

Use in fashionEdit

I've been using "significant event" > "heyday" to indicate the period when an item or style was popular or fashionable. These items are almost always subclasses, not instances, and now they get constraint violations because "significant event" cannot be applied to a subclass. How should we resolve this? - PKM (talk) 22:29, 20 April 2019 (UTC)

I'm just going to delete it. Surely it's pretty common for subclass items to have significant events (e.g., products.) Ghouston (talk) 03:18, 26 June 2019 (UTC)
Return to "P793" page.