Triple
T6685461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corner kick |
E152088
|
entity |
| Predicate | typicalPlayersInvolved |
P51071
|
FINISHED |
| Object | Corner taker |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Corner taker | Statement: [Corner kick, typicalPlayersInvolved, Corner taker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlayersInvolved Context triple: [Corner kick, typicalPlayersInvolved, Corner taker]
-
A.
playerInvolved
Indicates that a specific player participates in, is associated with, or takes part in a particular event, action, or situation.
-
B.
involvedActor
Indicates that an entity participates as an actor or participant in the referenced event, activity, or situation.
-
C.
intendedPlayers
Indicates the players for whom something (such as a game, item, or activity) is designed or meant to be used.
-
D.
hasPeopleInvolved
chosen
Indicates that certain people participate in, are associated with, or are otherwise involved in the referenced entity or event.
-
E.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:04 p.m.