Triple
T7611057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Marlowe Theatre |
E172235
|
entity |
| Predicate | demolishedPredecessor |
P51835
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [The Marlowe Theatre, demolishedPredecessor, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolishedPredecessor Context triple: [The Marlowe Theatre, demolishedPredecessor, 2009]
-
A.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
B.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
C.
previousBuildingDemolished
chosen
Indicates that a building which previously occupied the same site or fulfilled the same role has been demolished.
-
D.
demolishedAsPartOf
Indicates that one entity was demolished as a component or consequence of a larger demolition event or project involving another entity.
-
E.
demolishedOrAbsorbed
Indicates that one entity has ceased to exist independently because it was either physically destroyed or organizationally absorbed into another entity.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa221c848190b892ba1caec8d83a |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.