Triple
T31394941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke vs. North Carolina games |
E800839
|
entity |
| Predicate | associatedCoachUNC |
P207419
|
FINISHED |
| Object | Dean Smith |
E141389
|
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: Dean Smith | Statement: [Duke vs. North Carolina games, associatedCoachUNC, Dean Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCoachUNC Context triple: [Duke vs. North Carolina games, associatedCoachUNC, Dean Smith]
-
A.
dukeCoach
Indicates that one entity serves as a coach for a sports team or program associated with Duke University.
-
B.
VirginiaTechHeadCoach
Indicates the person who holds or has held the position of head coach at Virginia Tech.
-
C.
notableAssistantCoaches
Indicates that the subject has assistant coaches who are particularly distinguished or noteworthy in their roles.
-
D.
IndianaHeadCoach
Indicates that a person holds or has held the position of head coach for a sports team representing the state or institution of Indiana.
-
E.
coachOf
Indicates that one entity serves as the coach (trainer or manager) of another entity, typically a person or team.
- F. None of above. chosen
Provenance (5 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2ad248b6508190bccea55186414a61 |
completed | June 11, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:19 p.m.