Triple
T4625045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Shakespeare Theatre |
E101076
|
entity |
| Predicate | originalBuildingDestroyedBy |
P57500
|
FINISHED |
| Object | fire |
—
|
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: fire | Statement: [Royal Shakespeare Theatre, originalBuildingDestroyedBy, fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBuildingDestroyedBy Context triple: [Royal Shakespeare Theatre, originalBuildingDestroyedBy, fire]
-
A.
buildingsDestroyed
Indicates that one or more buildings have been damaged to the point of destruction as a result of some event or action.
-
B.
sufferedDestructionIn
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
C.
mainCityDestroyed
Indicates that the primary or central city associated with an entity has been destroyed.
-
D.
previousBuildingDemolished
Indicates that a building which previously occupied the same site or fulfilled the same role has been demolished.
-
E.
destroyedCity
Indicates that an entity has caused the complete or near-complete destruction of a city.
- F. None of above. chosen
Provenance (4 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a08ef488190af46418229309b0f |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:13 p.m.