Triple
T5347211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Opera House, Covent Garden |
E124085
|
entity |
| Predicate | predecessorBuildingOpened |
P33994
|
FINISHED |
| Object | 1732 |
—
|
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: 1732 | Statement: [Royal Opera House, Covent Garden, predecessorBuildingOpened, 1732]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorBuildingOpened Context triple: [Royal Opera House, Covent Garden, predecessorBuildingOpened, 1732]
-
A.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
B.
openedAsCurrentBuilding
Indicates that an entity began operating or was inaugurated in its current building or physical premises.
-
C.
openedAsPredecessor
chosen
Indicates that one entity was opened or began operation as the predecessor to another entity, which later replaced or succeeded it.
-
D.
successorBuildingOnSite
Indicates that one building directly replaces another on the same physical site or location.
-
E.
formerStationOnSiteOpened
Indicates that a former station located on the same site was opened at a specified time.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ede7c481908347d557aa4d19ad |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.