Triple
T26622688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dana Holgorsen |
E668244
|
entity |
| Predicate | roleAtOklahomaState |
P163452
|
FINISHED |
| Object | offensive coordinator |
—
|
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: offensive coordinator | Statement: [Dana Holgorsen, roleAtOklahomaState, offensive coordinator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtOklahomaState Context triple: [Dana Holgorsen, roleAtOklahomaState, offensive coordinator]
-
A.
roleAtWashingtonState
Indicates that an entity holds or held a specific role or position at Washington State.
-
B.
roleAtHouston
Indicates that an entity holds or held a specific role or position at an organization, institution, or context associated with Houston.
-
C.
roleInGeorgia
Indicates that an entity holds or has held a specific role, position, or function within the context of Georgia (such as its government, institutions, or organizations).
-
D.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
-
E.
roleAtOkinawa
Indicates the specific role, position, or function an entity held in relation to the event or context of Okinawa.
- F. None of above. chosen
Provenance (4 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 2:21 a.m.