Triple
T11598100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doak Campbell Stadium |
E275056
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object | Doak |
E834855
|
NE 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: Doak | Statement: [Doak Campbell Stadium, hasNickname, Doak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Doak Context triple: [Doak Campbell Stadium, hasNickname, Doak]
-
A.
Doak
chosen
Doak is a masculine given name most famously associated with American football star and Heisman Trophy winner Doak Walker.
-
B.
Tarkanian
Tarkanian is a surname most prominently associated with Jerry Tarkanian, the Hall of Fame college basketball coach known for his success at UNLV.
-
C.
Dungy
Dungy is the surname of Tony Dungy, a former NFL head coach and Super Bowl champion known for his leadership and advocacy on and off the field.
-
D.
Griese
Griese is a surname most prominently associated with Bob Griese, the Hall of Fame American football quarterback.
-
E.
Maclin
Maclin is a surname most notably associated with former NFL wide receiver Jeremy Maclin.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89549c870819086e16e9110bbad87 |
completed | April 10, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a7cad108819082eebb3ca130f5b8 |
completed | April 22, 2026, 10:49 a.m. |
Created at: April 8, 2026, 9:38 p.m.