Triple
T31426028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwyer Stadium |
E801663
|
entity |
| Predicate | originalStadiumDemolished |
P50097
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Dwyer Stadium, originalStadiumDemolished, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalStadiumDemolished Context triple: [Dwyer Stadium, originalStadiumDemolished, 1995]
-
A.
formerStadiumClosed
chosen
Indicates that a stadium, which previously served as the home venue for an entity, has been permanently closed.
-
B.
formerHomeStadium
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
C.
lastStadium
Indicates that one stadium is the final or most recent stadium associated with a particular entity, such as a team, event, or player.
-
D.
partOfFormerStadium
Indicates that one entity was a component or section of a stadium that no longer exists or is no longer in use.
-
E.
openedOnFormerStadiumSite
Indicates that something (such as a venue or facility) was opened on the site where a former stadium once stood.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00be8ee4bc8190b795d9606f0e490c |
completed | May 10, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_6a00bde163c88190867104bd08cac2ee |
completed | May 10, 2026, 5:18 p.m. |
Created at: April 30, 2026, 8:53 p.m.