Triple
T28968380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 NCAA Division I-A football championship |
E732102
|
entity |
| Predicate | decidingGameState |
P166259
|
FINISHED |
| Object | Arizona |
—
|
NE NERFINISHED |
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: Arizona | Statement: [1986 NCAA Division I-A football championship, decidingGameState, Arizona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingGameState Context triple: [1986 NCAA Division I-A football championship, decidingGameState, Arizona]
-
A.
decidingGameOf
Indicates that one event, action, or game serves as the decisive factor determining the outcome or result of another.
-
B.
decidingPlay
Indicates that an action or event serves as the critical play that determines the outcome of a game or contest.
-
C.
gameState
Indicates the current status or condition of a game at a particular point in time, including relevant rules, progress, and contextual information.
-
D.
decidingGameNumber
Indicates the specific game in a series whose outcome determines the overall winner of the series.
-
E.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 8:53 a.m.