Triple
T31804733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory Bell (Duke–North Carolina) rivalry |
E811840
|
entity |
| Predicate | trophyLocationWhenDukeWins |
P70454
|
FINISHED |
| Object | Duke University campus |
—
|
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: Duke University campus | Statement: [Victory Bell (Duke–North Carolina) rivalry, trophyLocationWhenDukeWins, Duke University campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyLocationWhenDukeWins Context triple: [Victory Bell (Duke–North Carolina) rivalry, trophyLocationWhenDukeWins, Duke University campus]
-
A.
trophyDisplayLocation
chosen
Indicates the place or setting where a trophy is presented, stored, or shown.
-
B.
trophyWonBy
Indicates that a particular trophy or award is obtained or earned by a specific entity (such as a person or team).
-
C.
WallOfChampionsLocation
Indicates the specific place where a Wall of Champions is situated or found.
-
D.
victoryLocation
Indicates the place or setting where a victory or triumph occurs.
-
E.
trophyCustodian
Indicates that one entity is responsible for holding, safeguarding, or managing a trophy on behalf of another entity or organization.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 11:42 p.m.