Property talk:P710

From Wikidata
Jump to navigation Jump to search

Documentation

participant
person, group of people or organization (object) that actively takes/took part in an event or process (subject). Preferably qualify with "object has role" (P3831). Use P1923 for participants that are teams.
Descriptionperson, group of people or organization that actively takes/took part in the event
Representsparticipant (Q56512863)
Data typeItem
Domain
According to this template: all kinds of events
According to statements in the property:
occurrence (Q1190554), fictional occurrence (Q14136353), mythical event (Q24336466), project (Q170584), race result (Q54933017), coalition (Q124964), agreement (Q321839), cooperative (Q4539), process (Q3249551), tournament (Q500834), sports competition (Q13406554), interview (Q178651), human (Q5), group of humans (Q16334295), system (Q58778), creative work season (Q70990126), podcast (Q24634210), television series episode (Q21191270), theater of war (Q718893) or robbery (Q53706)
When possible, data should only be stored as statements
ExampleSaudi-led intervention in the Yemeni civil war (Q19682450)Saudi Arabia (Q851)
First Continental Congress (Q252612)George Washington (Q23)
Eurovision Song Contest 2022 (Q96929880)Last Pizza Slice (Q110966462)
Ronde van Drenthe 2010 (Q50143442)Carla Swart (Q441419)
Tracking: usageCategory:Pages using Wikidata property P710 (Q26678449)
See alsoparticipating team (P1923), subject has role (P2868), candidate (P726), number of participants (P1132), debut participant (P2318), exhibited creator (P10661)
Lists
Proposal discussionProposal discussion
Current uses
Total872,171
Main statement858,42298.4% of uses
Qualifier13,7281.6% of uses
Reference21<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “occurrence (Q1190554), fictional occurrence (Q14136353), mythical event (Q24336466), project (Q170584), race result (Q54933017), coalition (Q124964), agreement (Q321839), cooperative (Q4539), process (Q3249551), tournament (Q500834), sports competition (Q13406554), interview (Q178651), human (Q5), group of humans (Q16334295), system (Q58778), creative work season (Q70990126), podcast (Q24634210), television series episode (Q21191270), theater of war (Q718893), robbery (Q53706): item must contain property “instance of (P31), subclass of (P279)” with classes “occurrence (Q1190554), fictional occurrence (Q14136353), mythical event (Q24336466), project (Q170584), race result (Q54933017), coalition (Q124964), agreement (Q321839), cooperative (Q4539), process (Q3249551), tournament (Q500834), sports competition (Q13406554), interview (Q178651), human (Q5), group of humans (Q16334295), system (Q58778), creative work season (Q70990126), podcast (Q24634210), television series episode (Q21191270), theater of war (Q718893), robbery (Q53706)” or their subclasses (defined using subclass of (P279)). (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/P710#Type Q1190554, Q14136353, Q24336466, Q170584, Q54933017, Q124964, Q321839, Q4539, Q3249551, Q500834, Q13406554, Q178651, Q5, Q16334295, Q58778, Q70990126, Q24634210, Q21191270, Q718893, Q53706, SPARQL
Contemporaries:
if [item A] has this property (participant (P710)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Boshin War (Q309184)
List of violations of this constraint: Database reports/Constraint violations/P710#Contemporary, SPARQL
Qualifiers “time played (P9140), member of sports team (P54), number of points/goals/set scored (P1351), number of points/goals attempted (P8884), ranking (P1352), country for sport (P1532), series ordinal (P1545), Program Component Score (P4826), Technical Element Score (P4815), together with (P1706), deductions (in figure skating) (P4825), object of statement has role (P3831), sport number (P1618), race time (P2781), stage reached (P2443), number of wins (P1355), number of losses (P1356), distinctive jersey (P2912), number of matches played/races/starts (P1350), number of points/goals conceded (P1359), number of draws/ties (P1357), position played on team / speciality (P413), laps completed (P5349), sports discipline competed in (P2416), duration (P2047), significant event (P793), jockey (P5317), point in time (P585), commanded by (P4791), object named as (P1932), end cause (P1534), points for (P1358), start time (P580), end time (P582), size of team at start (P2103), size of team at finish (P2105), award received (P166), has part(s) (P527), represents (P1268), wind speed (P5065), nature of statement (P5102), length (P2043), including (P1012), represented by (P1875), subject has role (P2868), affiliation (P1416), has characteristic (P1552), height (P2048), competition class (P2094), does not have characteristic (P6477), quantity (P1114), reason for preferred rank (P7452), reason for deprecated rank (P2241), wears (P3828), identity of object in context (P4626), allegiance (P945), has goal (P3712): 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/P710#allowed qualifiers, SPARQL
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P710#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/P710#Entity types
Conflicts with “instance of (P31): film (Q11424), animated series (Q581714), anime television series (Q63952888), television series (Q5398426): 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/P710#Conflicts with P31, SPARQL
Conflicts with “instance of (P31): disappearance (Q3030513), accident (Q171558), disaster (Q3839081), suicide (Q10737), explosion (Q179057), shooting (Q2252077): 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/P710#Conflicts with P31, SPARQL
Conflicts with “victim(s) (P8032): 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/P710#Conflicts with P8032, search, SPARQL
Conflicts with “perpetrator (P8031): 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/P710#Conflicts with P8031, search, SPARQL
Conflicts with “instance of (P31): human (Q5): 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/P710#Conflicts with P31, search, SPARQL
Conflicts with “instance of (P31): podcast episode (Q61855877), podcast (Q24634210): 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/P710#Conflicts with P31, SPARQL
Conflicts with “instance of (P31): musical work/composition (Q105543609), music track with vocals (Q55850593), music track without lyrics (Q55850643): 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/P710#Conflicts with P31, SPARQL
None of decision of the Supreme Court of Sweden (Q96482904): value must not be any of the specified items.
Replacement property: defendant (P1591), plaintiff (P1620)
Replacement 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/P710#none of, SPARQL
Value type “agent (Q24229398), group of living things (Q16334298), individual (Q795052): This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value agent (Q24229398), group of living things (Q16334298), individual (Q795052) (or a subclass thereof). (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/P710#Value type Q24229398, Q16334298, Q795052, SPARQL

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

Contemporaries:
if [item A] has this property (P710) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history.
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/P710#Contemporary, SPARQL

Usage discussion

[edit]

Regarding sporting events, the property can also be equipped with a qualifier to express the round or place that the participant reached. Properties like "champion", "runner-up", etc are used in many infoboxes for sporting events. For the Olympics, there are group items like Canada at the 2012 Summer Olympics (Q140982), so you don't have to list all 11,000+ athletes under one item; in order to be fully accurate, you would arguably need to introduce similar items for events like 2010 FIFA World Cup (Q176883), to list the actual squad members that participated.--Kompakt (talk) 08:15, 30 May 2013 (UTC)[reply]

I proposed above to have group items for events with a lot of participants, like the Olympics. As a matter of fact, we do have items already, e.g. Canada at the 2008 Summer Olympics (Q140854). So 2008 Summer Olympics (Q8567) would have "participants": Canada at the 2008 Summer Olympics (Q140854)", and within Canada at the 2008 Summer Olympics (Q140854), all members of that team would be listed using has part(s) (P527). Still you're right, this property could have a hundred values in some occasions, so grouping level could be necessary (e.g. "Canadian archers at the 2008 Olympics"). But on a closer look, proposal of creating such a property on the participants' side bears the just same problem: professional sportspeople usually take part in hundreds of events within their career.
But that's not my point. What is the mains idea behind this property? Using a qualifier like "ranking", it will it possible to describe the result of a sports event; we are to tell who won the event, who was second, etc. Taking the example above, we could use this for archery at the 2008 Summer Olympics (Q223519) to tell who got the gold medal, who was second, etc. As mentioned above, this is an infobox property for sport events in wikipedia, but could also be used to create result lists or even complete draws at some later point. All of this would hardly be possible when we have this information distributed at the participants - although you could arguably create queries to fetch such information, I don't think that's the best way to do it. The winner, the runner-up as well as other participants should be stored along with the event itself.
A final remark: that the Olympics are the most complicated case by far. Take an ordinary single-sport event like the Soccer World Cup instead: for 2022 FIFA World Cup (Q284163) you'd use "participant" to list all teams with single items like "Icelandic team at the 2022 FIFA World Cup", and then list all team members within team items using has part(s) (P527). Then none of these properties would have than (roughly) 30 values.--Kompakt (talk) 08:49, 16 July 2013 (UTC)[reply]

If 'participant' is to have qualifiers for the performance achieved (time in a race, points for decathlon etc.) and the ranking (1st, 2nd etc.) then we will need a separate for each competition. For the Olympics the item the whole competition can use participant (P710) to list all the teams with qualifiers for the number of medals each received however you need an item for each heat of each competition if you want to give the time each participant achieved. If you only want to record the times achieved by the finalists then you only need an item for the final but that leaves a lot of people achieving career best performances that don't get recorded here. Eventually, I believe, we will have items for every heat. Filceolaire (talk) 23:51, 18 April 2014 (UTC)[reply]

Use for elections

[edit]

I believe this property can also be used for candidates in elections so I have added that to the aliases. Filceolaire (talk) 23:52, 18 April 2014 (UTC)[reply]

I see candidate (P726) exists so I am withdrawing this suggestion. Filceolaire (talk) 23:06, 24 April 2014 (UTC)[reply]

bilateral relations

[edit]

Hi, there is some questions to be solved about the bilateral relation (Q15221623) items. UserːPopcorndude proposes to change country (P17) for participant (P710). This imply to enlarge the scale of participant (P710) to all relation (Q930933). It is also proposed to change the constraints of diplomatic mission sent (P531). If interested in this field, it is discussed here. Louperivois (talk) 16:52, 9 June 2015 (UTC)[reply]

Death of person/item about person

[edit]

Please see Property_talk:P3342#Link_"death_of_(person)"_to_item_about_(person).
--- Jura 12:11, 6 March 2018 (UTC)[reply]

Can participant (P710) be something else than people and organizations?

[edit]

In Eurovision Song Contest 1956 (Q171784), participant (P710) is used for songs (as it is a song competition). Is this a proper usage of participant (P710)? There are no violations against it, but is it good to do it that way? //Mippzon (talk) 17:56, 17 March 2018 (UTC)[reply]

I think a new property called "participating work" would be better (similar to how participating team (P1923) is a separate property). ―Jochem van Hees (talk) 12:02, 21 June 2021 (UTC)[reply]
I'd certainly consider objects like ships as being able to participate in battles. Vicarage (talk) 09:41, 9 September 2022 (UTC)[reply]

Constraint issue

[edit]

The dates of Battle of Sarhu (Q488547) and Li Rubai (Q707765) are not in conflict, mm-dd-yyyy for the former, and "year" recorded for the latter. Therefore, there should not be a constraint issue for Li Rubai (Q707765). jshieh (talk) 15:30, 28 June 2021 (UTC)[reply]

Cannot coexist with "number of casualties" - why?!

[edit]

The case of a naval battle. Two known participants (submarine vs. surface ship). Casualties duly counted and published. What's wrong with listing both "participants" and "number of casualties"? Any workaround, perhaps? Retired electrician (talk) 11:15, 1 December 2021 (UTC)[reply]

The description of winner (P1346) says it should not be used for wars or battles; I'm guessing the same applies for this property. What the alternative would be I don't know; something like conflict (P607) but then the inverse. @Trade: you added the constraint, do you maybe have some input? ―Jochem van Hees (talk) 14:38, 1 December 2021 (UTC)[reply]
My goal was mainly to stop people from using the property on items about murders and terror attacks. @Jochem van Hees: --Trade (talk) 19:35, 5 December 2021 (UTC)[reply]
… because? What’s wrong in stating someone participated in an accident with a defined number of victims/survivors? (E.g. Air Florida Flight 90 (Q2372837), Munich air disaster (Q308923), sinking of DS Trym (Q19399022).) Or maybe even vehicles participating in a collision? (E.g. Sinking of Hableány (Q64164118), Moby Prince disaster (Q3709247).) I don’t think this is a good constraint. --Mormegil (talk) 16:11, 19 March 2023 (UTC)[reply]

Participant_in or conflict

[edit]

A warship's role in a battle is notable, less so for wars. My preference is for it to use participant (P710) rather than conflict (P607) which I'd use for wars, the distinction between tactical and strategic. Both battles and wars don't mention ships in their participant lists, so it seems a good property for a ship. Vicarage (talk) 09:54, 9 September 2022 (UTC)[reply]

Allow commanded_by as a qualifier

[edit]

As battles use participant (P710) in its sense as belligerent, I think that commanded by (P4791) should be added as a valid qualifier. So the Battle of Trafalgar has participant United Kingdom commanded by Horatio Nelson. Currently Nelson is a direct participant, but the command structure seems better. Vicarage (talk) 13:26, 6 May 2023 (UTC)[reply]

No dissent, so done Vicarage (talk) 20:39, 13 May 2023 (UTC)[reply]

Participant in instance of interview

[edit]

I'm scoping out creating Wikidata items for a series of oral history interviews. I had planned to use Participant with qualifier object has role for interviewer and interviewee - but am getting a constraint error message. Looking at the page for Participant I'm a bit confused as using it with an instance of an interview seems to be listed as possible and as a constraint. Would a more experienced editor be able to advise please? Example: Q118314152. On this item I've added what looks like an alternative with the interviewer and interviewee names in a significant person statement. I'm wondering what the most appropriate option is. Thanks HelsKRW (talk) 14:11, 12 May 2023 (UTC)[reply]

The constraint was added by User:Gymnicus. I understand the basic idea of forcing cast member (P161) instead of participant (P710) for e.g. film (Q11424); however, for interview (Q178651), it is debatable. Is it really better to use cast member (P161) for interviews? I doubt that… so I’d be inclined to remove interview (Q178651) from the constraint. --Mormegil (talk) 14:35, 12 May 2023 (UTC)[reply]
Participant seems sensible. The use of significant person in the example feels clumsy by comparison. Vicarage (talk) 14:46, 12 May 2023 (UTC)[reply]
Thanks @Vicarage I've done a SPARQL query to find some other interviews and they also use participant with qualifier object has role interviewer and interviewee, so it looks as if I'm not the only one who would like to use participant with interview in this way - and it does seem less clumsy than significant person. HelsKRW (talk) 09:29, 15 May 2023 (UTC)[reply]
Thank you @Mormegil. Yes, cast member would not seem appropriate in this case as it is an oral history interview. How does it work to remove interview from the constraint - is that something that a more senior editor would do? I don't want to remove a constraint if I don't have the right to do that! If possible I would prefer to remove the constraint first, rather than create a lot of Qids which contain error messages! HelsKRW (talk) 09:28, 15 May 2023 (UTC)[reply]
I've removed the 'conflicts-with constraint' of P31=Q178651. diff It is reasonable to use participant (P710) as it is being used in e.g. Q118314152#P710. The constraint seems to have been added without thinking through situations in which it is valid. Courtesy ping @Gymnicus:. --Tagishsimon (talk) 13:32, 17 May 2023 (UTC)[reply]
It's been a while since it was added, so I don't remember exactly the circumstances of how it came about. But the basic intention behind it was the proximity of talk show, podcast and interview. Participants must not be used for the first things mentioned, which is why I think it makes sense to do this for interviews as well. But then you also have to generalize the two properties P5030 and P371 and I didn't do that. So I understand that it should and has been rolled back. --Gymnicus (talk) 15:52, 17 May 2023 (UTC)[reply]
Thanks for your help with this everyone - very much appreciate it HelsKRW (talk) 08:25, 18 May 2023 (UTC)[reply]

contemporary date constraint does not consider year 1805 to include 21 October 1805

[edit]

Bug https://phabricator.wikimedia.org/T349971 raised as

Battle of Trafalgar (Q171416) has error

contemporary constraint The entities Battle of Trafalgar and Horatio Nelson should be contemporary to be linked through participant, but the latest end value of Horatio Nelson is 1805 and the earliest start value of Battle of Trafalgar is 21 October 1805.

This is also true of states, see Battle of Waterloo (Q48314)

Expected behaviour: comparison of dates with different levels of precision should always expand the less qualified date to the start or end of the period depending on the comparison. Vicarage (talk) 11:02, 29 October 2023 (UTC)[reply]

Sadly this bug was merged with https://phabricator.wikimedia.org/T168379 which has been known since 2017, so I doubt anyone else cares Vicarage (talk) 14:13, 29 October 2023 (UTC)[reply]

isn't 972 part of 10th century?

[edit]

Not sure of the reason of "problem" for dates here (not able to attach screenshot). The participant Emperor Shengzong of Liao in this item, Q706428, has 972-1031 for birth and death dates? Aren't the dates in the range of 10 CE and 11 CE? jshieh (talk) 18:31, 6 November 2023 (UTC)[reply]

"10 CE" is the year 10 (in the first century), not the 10th century!
Mormegil (talk) 10:07, 7 November 2023 (UTC)[reply]
got it! Thanks. PS: system still does not like 10. century...
dates
jshieh (talk) 17:47, 20 November 2023 (UTC)[reply]
Yeah, that one is the well-known bug in the contemporary constraint implementation, see phab:T168379. But it seems to me the dates in Q706428 can have better precision, I have changed them according to the enwiki article (listed as the reference), so the constraint error went away. --Mormegil (talk) 11:11, 22 November 2023 (UTC)[reply]