Triple
T6438885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heisman Trophy |
E129967
|
entity |
| Predicate | ArchieGriffinAwards |
P20896
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Heisman Trophy, ArchieGriffinAwards, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ArchieGriffinAwards Context triple: [Heisman Trophy, ArchieGriffinAwards, 2]
-
A.
quarterbackAward
Indicates that an entity has received an award specifically recognizing performance or achievement in the role of quarterback.
-
B.
Pac12PlayerOfTheYear
Indicates that the subject was selected as the Pac-12 Conference Player of the Year in a given season.
-
C.
HeismanTrophyWinner
chosen
Indicates that the subject is the recipient of the Heisman Trophy, awarded annually to the most outstanding player in U.S. college football.
-
D.
runningBackAward
Indicates that an entity has received an award specifically recognizing performance or achievement in the role of running back.
-
E.
defensiveRookieOfTheYear
Indicates that the subject was awarded the Defensive Rookie of the Year honor in a given league 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06965a5d48190a5860da9e22dc6e0 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.