Triple
T31520521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring cycle |
E804193
|
entity |
| Predicate | completeCyclePremiereLocation |
P3172
|
FINISHED |
| Object | Bayreuth Festspielhaus |
—
|
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: Bayreuth Festspielhaus | Statement: [Ring cycle, completeCyclePremiereLocation, Bayreuth Festspielhaus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completeCyclePremiereLocation Context triple: [Ring cycle, completeCyclePremiereLocation, Bayreuth Festspielhaus]
-
A.
firstCompleteCyclePremiere
Indicates that an entity’s first complete cycle (e.g., season, series, or full run) is being presented or released for the first time.
-
B.
premiereLocation
chosen
Indicates the place where something (such as a film, play, or event) is first publicly presented or debuted.
-
C.
secondPartPremiereLocation
Indicates the location where the second part of something (such as a work, event, or series) first premiered or was initially presented.
-
D.
workCompletePremierePlace
Indicates that a work was fully completed at the place where it premiered.
-
E.
startingPark
Indicates that an entity begins or initiates its activity, route, or presence from a specified park.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 30, 2026, 9:55 p.m.