Triple
T7352506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covent Garden Theatre |
E169536
|
entity |
| Predicate | thirdBuildingOpened |
P76759
|
FINISHED |
| Object | 1858 |
—
|
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: 1858 | Statement: [Covent Garden Theatre, thirdBuildingOpened, 1858]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdBuildingOpened Context triple: [Covent Garden Theatre, thirdBuildingOpened, 1858]
-
A.
openedAsCurrentBuilding
Indicates that an entity began operating or was inaugurated in its current building or physical premises.
-
B.
reopenedInNewBuilding
Indicates that an entity, after being closed or relocated, has resumed operations in a different, newly constructed building.
-
C.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
D.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
E.
openedFirstBoutiqueIn
Indicates that an entity established its first boutique or retail store in a specified location.
- 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1379cac81908b35e617c44c7b13 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:05 p.m.