Triple
T8259411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odesa Opera and Ballet Theater |
E193154
|
entity |
| Predicate | currentBuildingInaugurated |
P14622
|
FINISHED |
| Object | 1887 |
—
|
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: 1887 | Statement: [Odesa Opera and Ballet Theater, currentBuildingInaugurated, 1887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentBuildingInaugurated Context triple: [Odesa Opera and Ballet Theater, currentBuildingInaugurated, 1887]
-
A.
buildingInaugurationDate
chosen
Indicates the date on which a building was formally opened or inaugurated.
-
B.
inauguratedWith
Indicates that an event, position, or institution was formally initiated or opened through a specific ceremony, action, or accompanying element.
-
C.
inauguralVenue
Indicates the location or facility where an event, organization, or activity was first officially launched or held.
-
D.
currentBuilding
Indicates that an entity is located in, associated with, or belongs to the building that is relevant in the current context.
-
E.
inauguratedFor
Indicates that a formal ceremony or event was held to officially begin or dedicate something specifically for a particular entity, role, or purpose.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78fe5e2c819080741ea24bae0807 |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.