Triple
T6946674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Cricket World Cup final |
E160815
|
entity |
| Predicate | tossDecision |
P2273
|
FINISHED |
| Object | bat |
—
|
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: bat | Statement: [2015 Cricket World Cup final, tossDecision, bat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tossDecision Context triple: [2015 Cricket World Cup final, tossDecision, bat]
-
A.
coinTossChoice
Indicates the outcome selected or assigned to a participant in a coin toss (e.g., heads or tails).
-
B.
coinTossParticipant
Indicates that an entity takes part in a coin toss event, either as the initiator or as one of the involved participants.
-
C.
decidesOn
chosen
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
coinTossWinner
Indicates which participant is the winner resulting from a specific coin toss event.
-
E.
winnerThrows
Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.