Triple
T31394922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke vs. North Carolina games |
E800839
|
entity |
| Predicate | DukeHomeArena |
P171817
|
FINISHED |
| Object | Cameron Indoor Stadium |
—
|
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: Cameron Indoor Stadium | Statement: [Duke vs. North Carolina games, DukeHomeArena, Cameron Indoor Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DukeHomeArena Context triple: [Duke vs. North Carolina games, DukeHomeArena, Cameron Indoor Stadium]
-
A.
cityOfConsecoFieldhouse
Indicates that a given city is the location of Conseco Fieldhouse.
-
B.
FinalFourVenue
Indicates that a venue is the designated location where the Final Four round of a tournament is held.
-
C.
homeArenaOfPrinceton
Indicates that a particular sports arena or venue serves as the home arena for Princeton.
-
D.
franchiseCenter
Indicates that one entity serves as the central or primary hub for a network of related franchise entities.
-
E.
replacedAsPrimaryBasketballVenueBy
Indicates that one basketball venue ceased to be the main or primary location for games or events and was succeeded in that role by another venue.
- 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_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. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 29, 2026, 9:19 p.m.