Triple
T9760448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Stick |
E236654
|
entity |
| Predicate | demolitionStatusOfStadium |
P48476
|
FINISHED |
| Object | demolished |
—
|
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: demolished | Statement: [The Stick, demolitionStatusOfStadium, demolished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolitionStatusOfStadium Context triple: [The Stick, demolitionStatusOfStadium, demolished]
-
A.
demolitionStatus
chosen
Indicates the current state or progress of a demolition process affecting an entity.
-
B.
destructionStatus
Indicates the condition or extent to which something has been damaged, ruined, or rendered unusable.
-
C.
hasDemolitionOrDestruction
Indicates that one entity causes, undergoes, or is associated with the demolition or destruction of another entity.
-
D.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
E.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda04ad9008190badfcebe2072ab83 |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.