Triple
T36270965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Over |
E892671
|
entity |
| Predicate | teamBattingOrder |
P146534
|
FINISHED |
| Object | usually decided by a coin toss |
—
|
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: usually decided by a coin toss | Statement: [Super Over, teamBattingOrder, usually decided by a coin toss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamBattingOrder Context triple: [Super Over, teamBattingOrder, usually decided by a coin toss]
-
A.
battedInOrderWith
Indicates that two batters took their turns at the plate in the same batting order or sequence within a game or lineup.
-
B.
battingOrderFlexibility
Indicates the degree to which the sequence of batters in a lineup can be rearranged or adjusted without violating rules or significantly reducing effectiveness.
-
C.
battingOrderRules
chosen
Indicates the rules or constraints that govern the sequence in which players are assigned to bat.
-
D.
battingTeam
Indicates which team is currently performing the batting action in a game or play situation.
-
E.
teamLineup
Indicates the assignment and ordering of participants or members that make up a specific team configuration for an event or activity.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.