Triple
T31394923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke vs. North Carolina games |
E800839
|
entity |
| Predicate | NorthCarolinaHomeArena |
P135416
|
FINISHED |
| Object | Dean E. Smith Center |
—
|
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: Dean E. Smith Center | Statement: [Duke vs. North Carolina games, NorthCarolinaHomeArena, Dean E. Smith Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NorthCarolinaHomeArena Context triple: [Duke vs. North Carolina games, NorthCarolinaHomeArena, Dean E. Smith Center]
-
A.
homeArenaCarolina
chosen
Indicates that the specified arena serves as the home venue for the Carolina team.
-
B.
NCOrank
Indicates a hierarchical ranking relationship between entities within the context of a non-commissioned officer (NCO) rank structure.
-
C.
tournamentRegionOfNorthCarolina
Indicates that a tournament is located in or associated with the North Carolina region.
-
D.
cityOfAmericanAirlinesArena
Indicates the city in which the American Airlines Arena is located.
-
E.
cityOfChampionHomeArena
Indicates that a city is the home location of the arena where a champion’s team or individual competitor plays or competes.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.