Triple
T36270977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Over |
E892671
|
entity |
| Predicate | battingSideSelection |
P185395
|
FINISHED |
| Object | decided by toss-winning captain |
—
|
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: decided by toss-winning captain | Statement: [Super Over, battingSideSelection, decided by toss-winning captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingSideSelection Context triple: [Super Over, battingSideSelection, decided by toss-winning captain]
-
A.
battingType
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
B.
battingSideForHomeRuns
Indicates the batting side (e.g., left-handed, right-handed, switch) from which a player hit their home runs.
-
C.
battedBy
Indicates that an entity is the one who performed the batting action on another entity (e.g., a ball being batted by a player).
-
D.
battingPosition
Indicates the specific order or spot in which a player appears in a batting lineup or batting order.
-
E.
battingHand
Indicates the handedness a player uses when batting, such as right-handed, left-handed, or switch.
- F. None of above. chosen
Provenance (4 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:09 p.m.