Triple
T2904343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Arkansas Razorbacks football |
E62726
|
entity |
| Predicate | hasHeismanTrophyWinner |
P20896
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [University of Arkansas Razorbacks football, hasHeismanTrophyWinner, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeismanTrophyWinner Context triple: [University of Arkansas Razorbacks football, hasHeismanTrophyWinner, no]
-
A.
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.
-
B.
heismanTrophyFinalist
Indicates that a person was selected as one of the finalists considered for the Heisman Trophy award in a given year.
-
C.
HeismanTrophyYear
Indicates the specific year in which an entity received or was associated with the Heisman Trophy award.
-
D.
hasWonBowlGame
Indicates that a team or individual has achieved victory in a specific bowl game competition.
-
E.
collegeFootballHallOfFameId
Indicates the unique identifier assigned to an individual or entity in the College Football Hall of Fame database.
- 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0cd68d48190aea4afbdaed2d4bc |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.