Triple
T5384453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buxton Opera House |
E113167
|
entity |
| Predicate | reopenedAsLiveTheatre |
P29252
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Buxton Opera House, reopenedAsLiveTheatre, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsLiveTheatre Context triple: [Buxton Opera House, reopenedAsLiveTheatre, 1979]
-
A.
reopenedAsTheater
chosen
Indicates that a venue or building, previously closed or used differently, has been opened again specifically to function as a theater.
-
B.
reopenedAsDerbyTheatre
Indicates that an entity, after having been closed or repurposed, was subsequently reopened under the name or identity of Derby Theatre.
-
C.
reopenedAsConcertHall
Indicates that a previously closed or differently purposed venue has been opened again specifically to function as a concert hall.
-
D.
revisedPremiereTheatre
Indicates that an entity has updated or altered the initial theatrical premiere of another entity (such as a film, play, or performance).
-
E.
theatreOf
Indicates that an event, action, or operation takes place within or is primarily associated with a particular theatre or venue.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86f39edc81908e53973cef1bc0f3 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.