Triple
T26394515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoom-Zoom Stadium |
E663511
|
entity |
| Predicate | formerStadiumReplaced |
P61007
|
FINISHED |
| Object | Hiroshima Municipal 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: Hiroshima Municipal Stadium | Statement: [Zoom-Zoom Stadium, formerStadiumReplaced, Hiroshima Municipal Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerStadiumReplaced Context triple: [Zoom-Zoom Stadium, formerStadiumReplaced, Hiroshima Municipal Stadium]
-
A.
formerStadiumClosed
Indicates that a stadium, which previously served as the home venue for an entity, has been permanently closed.
-
B.
replacedStadiumForTeam
chosen
Indicates that one stadium succeeded and took over the role of another as the home venue for a particular team.
-
C.
formerHomeStadium
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
D.
replacedByAsMainFootballVenue
Indicates that one football venue has been superseded by another as the primary location for hosting football events.
-
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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 26, 2026, 11:28 p.m.