Triple
T8259418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odesa Opera and Ballet Theater |
E193154
|
entity |
| Predicate | hasHorseshoeAuditorium |
P17368
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Odesa Opera and Ballet Theater, hasHorseshoeAuditorium, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHorseshoeAuditorium Context triple: [Odesa Opera and Ballet Theater, hasHorseshoeAuditorium, true]
-
A.
hasAuditorium
chosen
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
B.
hasOrchestraPit
Indicates that a venue or performance space includes a designated orchestra pit area for musicians.
-
C.
auditoriumType
Indicates the specific kind or category of auditorium associated with an entity.
-
D.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
E.
hasOrchestraPitCapacity
Indicates the number of people that can be accommodated in the orchestra pit associated with a venue or performance space.
- 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.