Triple
T11891611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Football Stadium |
E282928
|
entity |
| Predicate | demolitionOfPredecessorCompleted |
P51835
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Sydney Football Stadium, demolitionOfPredecessorCompleted, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolitionOfPredecessorCompleted Context triple: [Sydney Football Stadium, demolitionOfPredecessorCompleted, 2019]
-
A.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
-
B.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
C.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
D.
previousBuildingDemolished
chosen
Indicates that a building which previously occupied the same site or fulfilled the same role has been demolished.
-
E.
demolishedAfterEvent
Indicates that one entity (typically a structure) was demolished after the occurrence of a specified event.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a3f7548190adfb567f060a175a |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.