Triple
T21009483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayreuth Festival |
E517506
|
entity |
| Predicate | orchestraPitType |
P14648
|
FINISHED |
| Object | covered orchestra pit |
—
|
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: covered orchestra pit | Statement: [Bayreuth Festival, orchestraPitType, covered orchestra pit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orchestraPitType Context triple: [Bayreuth Festival, orchestraPitType, covered orchestra pit]
-
A.
hasOrchestraPit
chosen
Indicates that a venue or performance space includes a designated orchestra pit area for musicians.
-
B.
hasOrchestraPitCapacity
Indicates the number of people that can be accommodated in the orchestra pit associated with a venue or performance space.
-
C.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
D.
orchestralRole
Indicates the specific function or position an entity holds within an orchestra (e.g., conductor, principal violin, section player).
-
E.
orchestrationIncludes
Indicates that one orchestration contains, incorporates, or makes use of another orchestration as part of its overall structure or process.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3edc548190987a6c2c9936286a |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.