Triple
T6136947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado Buffaloes football |
E136856
|
entity |
| Predicate | HeismanTrophyWinnerSeason |
P26245
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Colorado Buffaloes football, HeismanTrophyWinnerSeason, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HeismanTrophyWinnerSeason Context triple: [Colorado Buffaloes football, HeismanTrophyWinnerSeason, 1994]
-
A.
HeismanTrophyWinner
Indicates that the subject is the recipient of the Heisman Trophy, awarded annually to the most outstanding player in U.S. college football.
-
B.
HeismanTrophyYear
chosen
Indicates the specific year in which an entity received or was associated with the Heisman Trophy award.
-
C.
heismanTrophyFinalist
Indicates that a person was selected as one of the finalists considered for the Heisman Trophy award in a given year.
-
D.
hasHeismanTrophies
Indicates that the subject has won one or more Heisman Trophy awards.
-
E.
quarterbackAward
Indicates that an entity has received an award specifically recognizing performance or achievement in the role of quarterback.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c8211d48190bc10675ba6707150 |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.