Triple
T33259456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alice Busch Opera Theater |
E851469
|
entity |
| Predicate | mainStageFor |
P23322
|
FINISHED |
| Object | Glimmerglass Festival |
—
|
NE NERFINISHED |
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: Glimmerglass Festival | Statement: [Alice Busch Opera Theater, mainStageFor, Glimmerglass Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStageFor Context triple: [Alice Busch Opera Theater, mainStageFor, Glimmerglass Festival]
-
A.
isMainStageOf
chosen
Indicates that one entity serves as the primary or central stage or platform on which the other entity occurs, is presented, or is featured.
-
B.
primaryStage
Indicates that something is in its main or initial phase or level within a multi-stage process or system.
-
C.
initialStage
Indicates that one entity represents the first or starting phase in a sequence, process, or development of another entity.
-
D.
servesStage
Indicates that an entity functions as a stage or phase within a larger process, sequence, or workflow.
-
E.
focusStage
Indicates that an entity is currently at, or associated with, a particular stage or phase of focus within a process or workflow.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:31 a.m.