Triple
T15919258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kokuritsu Kyōgijō |
E386048
|
entity |
| Predicate | demolitionOfPreviousStadium |
P51835
|
FINISHED |
| Object | 2015 |
—
|
LITERAL FINISHED |
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: 2015 | Statement: [Kokuritsu Kyōgijō, demolitionOfPreviousStadium, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolitionOfPreviousStadium Context triple: [Kokuritsu Kyōgijō, demolitionOfPreviousStadium, 2015]
-
A.
formerStadiumClosed
Indicates that a stadium, which previously served as the home venue for an entity, has been permanently closed.
-
B.
demolishedAsPartOf
Indicates that one entity was demolished as a component or consequence of a larger demolition event or project involving another entity.
-
C.
previousBuildingDemolished
chosen
Indicates that a building which previously occupied the same site or fulfilled the same role has been demolished.
-
D.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
E.
demolishedToMakeWayFor
Indicates that one entity was intentionally destroyed or removed in order to create space for another entity or development.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.