Triple
T11196368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle in Miami game on December 9, 2018 |
E264930
|
entity |
| Predicate | decidingPlayStartYardLine |
P97806
|
FINISHED |
| Object | Miami 31-yard line |
—
|
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: Miami 31-yard line | Statement: [Miracle in Miami game on December 9, 2018, decidingPlayStartYardLine, Miami 31-yard line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingPlayStartYardLine Context triple: [Miracle in Miami game on December 9, 2018, decidingPlayStartYardLine, Miami 31-yard line]
-
A.
decidingPlayBallCarrier
Indicates that an agent is determining or designating which player will act as the ball carrier in a play.
-
B.
decidingPlay
Indicates that an action or event serves as the critical play that determines the outcome of a game or contest.
-
C.
decidingPlayOffenseTeam
Indicates that an entity is choosing or determining which team will play on offense.
-
D.
interceptionYardLine
Indicates the yard line on the field where an interception occurs during a play.
-
E.
decidingPlayFumbleForcedBy
Indicates that a deciding play in a game is characterized by a fumble that was forced by a particular entity (e.g., player or team).
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c082fc8190866c574f698b59ef |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.