Triple
T23808795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timeball Station site |
E589788
|
entity |
| Predicate | towerDemolished |
P132139
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Timeball Station site, towerDemolished, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerDemolished Context triple: [Timeball Station site, towerDemolished, 2011]
-
A.
towerDemolishedIn
chosen
Indicates that a tower was demolished at, or during an event occurring in, a specified location or time.
-
B.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
C.
mostStructuresDemolished
Indicates that the subject is the entity responsible for demolishing the greatest number of structures within a given context or set.
-
D.
towerCollapsedIn
Indicates that a tower underwent structural failure and collapsed at or within a specified location or context.
-
E.
demolishedOrDestroyed
Indicates that one entity has caused another entity to be torn down, ruined, or rendered unusable, typically through deliberate demolition or destructive force.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c753c46081908b3c9e5c2517b051 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.