Triple
T31804712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory Bell (Duke–North Carolina) rivalry |
E811840
|
entity |
| Predicate | homeStadiumDuke |
P172912
|
FINISHED |
| Object | Wallace Wade 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: Wallace Wade Stadium | Statement: [Victory Bell (Duke–North Carolina) rivalry, homeStadiumDuke, Wallace Wade Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumDuke Context triple: [Victory Bell (Duke–North Carolina) rivalry, homeStadiumDuke, Wallace Wade Stadium]
-
A.
DukeHomeArena
Indicates that a specified sports team or program uses a particular arena as its home venue at Duke University.
-
B.
cityOfConsecoFieldhouse
Indicates that a given city is the location of Conseco Fieldhouse.
-
C.
homeArenaOfPrinceton
Indicates that a particular sports arena or venue serves as the home arena for Princeton.
-
D.
notableDuke
Indicates that a person holds or held the title of duke and is distinguished or prominent in some notable way.
-
E.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:42 p.m.