Triple
T25774333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Dey cheer |
E649102
|
entity |
| Predicate | previousStadiumAssociation |
P901
|
FINISHED |
| Object | Riverfront 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: Riverfront Stadium | Statement: [Who Dey cheer, previousStadiumAssociation, Riverfront Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStadiumAssociation Context triple: [Who Dey cheer, previousStadiumAssociation, Riverfront Stadium]
-
A.
formerHomeStadium
chosen
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
B.
predecessorClubAssociation
Indicates that one club or team previously existed in place of, or was succeeded by, another club or team in an organizational or historical lineage.
-
C.
associatedStadiums
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
-
D.
associatedWithStadiumNameHistory
Indicates that there is a relationship between an entity and the historical or past names of a stadium with which it has been associated.
-
E.
hostStadiumPreviousName
Indicates that a stadium previously had a different official name before its current one.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 22, 2026, 5:33 a.m.