Triple
T28968388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 NCAA Division I-A football championship |
E732102
|
entity |
| Predicate | decidingGameOutcomeType |
P10213
|
FINISHED |
| Object | upset |
—
|
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: upset | Statement: [1986 NCAA Division I-A football championship, decidingGameOutcomeType, upset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingGameOutcomeType Context triple: [1986 NCAA Division I-A football championship, decidingGameOutcomeType, upset]
-
A.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
B.
gameOutcome
chosen
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
C.
decidingGameOf
Indicates that one event, action, or game serves as the decisive factor determining the outcome or result of another.
-
D.
decidingGameState
Indicates a game state in which a decisive outcome is determined, such as a win, loss, or final resolution of the game.
-
E.
decidingGameLoser
Indicates that the referenced entity is the loser in the decisive or final game that determines the overall outcome of a series or competition.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 8:53 a.m.