Wikidata:Property proposal/role in event
Jump to navigation
Jump to search
role in event[edit]
Originally proposed at Wikidata:Property proposal/Generic
Not done
| Description | event class for which the item describes a role |
|---|---|
| Data type | Item |
| Allowed values | occurrence (Q1190554) |
| Example 1 | eater (Q20984678)role in eventeating (Q213449) |
| Example 2 | food (Q2095)role in eventeating (Q213449) |
| Example 3 | Q_communicator_in_communicationrole in event communication (Q11024) |
| Example 4 | Q_content_in_communicationrole in event communication (Q11024) |
| Example 5 | Q_hearer_in_communicationrole in event communication (Q11024) |
| Source | initially based on PropBank, but extensible as needed |
| Planned use | add to (possibly newly created) items describing event participants |
| Expected completeness | always incomplete (Q21873886) |
| See also | predicate for (P9970), has thematic relation (P9971) |
Motivation[edit]
See our property proposal “event role” and project Events and Role Frames. This is the inverse of “event role”.
This is one of the five proposed properties that should be considered together: "event role", "role in event", "selectional preference", "event argument", and "argument type".
Anatole Gershman (talk) 21:37, 28 November 2023 (UTC)
Discussion[edit]
Comment A. Inverses really aren't necessary or recommended in Wikidata; however they may be useful in cases where one side of a relation may have a high cardinality; can you explain why you think an inverse is necessary here? B. It would be much better if your examples involved existing Wikidata items rather than proposed new ones. How is this property to be made useful if the items involved are not connected to the rest of Wikidata somehow? ArthurPSmith (talk) 16:57, 30 November 2023 (UTC)
- Reply A. You are right, strictly speaking, inverses aren't necessary even though they are rather common. One argument for having an inverse link is computational efficiency. B. Unfortunately, there are not many existing items in Wikidata that can be used as event roles, e.g., there is no "eater in eating". A few items such as assassin (Q55983771) could be used to describe the perpetrator in assassination (Q3882219). They are connected by event-specific properties: practiced by (P3095) and the "inverse" field of this occupation (P425). We are proposing a more general solution that applies to all events. In the case of assassin (Q55983771), we could re-use this item instead of creating "Q_assassin_in_assassination". Also note that currently, there is no statement or item describing the victim of assassination (Q3882219). --Anatole Gershman (talk) 22:54, 30 November 2023 (UTC)
- We agree that the inverse property isn't strictly necessary. Another justification is that events are quite often invoked indirectly through references to prototypical roles, as in "The class was so disruptive that the teacher only got through half of the material." This clearly describes a teaching event, but could most easily be accessed by using the inverse "role in event" property from teacher to teach. MarthaStonePalmer (talk) 18:13, 7 December 2023 (UTC)
- @ArthurPSmith:, would you like to give your final opinion based on the response? @Swpb: it looks you are not in favor of this proposal! am I right? Regards, ZI Jony (Talk) 06:52, 8 April 2024 (UTC)
Oppose I don't see any need for this. ArthurPSmith (talk) 14:47, 8 April 2024 (UTC)
- @ArthurPSmith:, would you like to give your final opinion based on the response? @Swpb: it looks you are not in favor of this proposal! am I right? Regards, ZI Jony (Talk) 06:52, 8 April 2024 (UTC)
- We agree that the inverse property isn't strictly necessary. Another justification is that events are quite often invoked indirectly through references to prototypical roles, as in "The class was so disruptive that the teacher only got through half of the material." This clearly describes a teaching event, but could most easily be accessed by using the inverse "role in event" property from teacher to teach. MarthaStonePalmer (talk) 18:13, 7 December 2023 (UTC)
- Reply A. You are right, strictly speaking, inverses aren't necessary even though they are rather common. One argument for having an inverse link is computational efficiency. B. Unfortunately, there are not many existing items in Wikidata that can be used as event roles, e.g., there is no "eater in eating". A few items such as assassin (Q55983771) could be used to describe the perpetrator in assassination (Q3882219). They are connected by event-specific properties: practiced by (P3095) and the "inverse" field of this occupation (P425). We are proposing a more general solution that applies to all events. In the case of assassin (Q55983771), we could re-use this item instead of creating "Q_assassin_in_assassination". Also note that currently, there is no statement or item describing the victim of assassination (Q3882219). --Anatole Gershman (talk) 22:54, 30 November 2023 (UTC)
- Comment Per my comment on Wikidata:Property proposal/event role, part of (P361) may be able to fill this role. Swpb (talk) 21:22, 4 December 2023 (UTC)
- Reply See my reply in Wikidata:Property proposal/event role. --Anatole Gershman (talk) 22:54, 13 December 2023 (UTC)
Support, an important property for the connectivity of Wikidata.--Arbnos (talk) 20:54, 12 January 2024 (UTC)
Not done, no consensus of proposed property at this time based on the above discussion. Regards, ZI Jony (Talk) 13:48, 19 April 2024 (UTC)
