Triple
T37001336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke vs. Michigan State (2015 NCAA Final Four) |
E915357
|
entity |
| Predicate | dukeConference |
P187261
|
FINISHED |
| Object | Atlantic Coast Conference |
—
|
NE NERFINISHED |
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: Atlantic Coast Conference | Statement: [Duke vs. Michigan State (2015 NCAA Final Four), dukeConference, Atlantic Coast Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dukeConference Context triple: [Duke vs. Michigan State (2015 NCAA Final Four), dukeConference, Atlantic Coast Conference]
-
A.
DukeHomeArena
Indicates that a specified sports team or program uses a particular arena as its home venue at Duke University.
-
B.
notableDuke
Indicates that a person holds or held the title of duke and is distinguished or prominent in some notable way.
-
C.
recordOfDukeBeforeGame
Indicates the performance record or statistics associated with Duke prior to a specific game.
-
D.
dukeCoach
Indicates that one entity serves as a coach for a sports team or program associated with Duke University.
-
E.
homeStadiumDuke
Indicates that the specified stadium serves as the home venue for the Duke team or organization.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.