Triple
T35489512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neues Deutsches Theater, Prague |
E1025689
|
entity |
| Predicate | hasTypeOfOrchestraPit |
P14648
|
FINISHED |
| Object | large opera 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: large opera orchestra pit | Statement: [Neues Deutsches Theater, Prague, hasTypeOfOrchestraPit, large opera orchestra pit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfOrchestraPit Context triple: [Neues Deutsches Theater, Prague, hasTypeOfOrchestraPit, large opera orchestra pit]
-
A.
hasOrchestraPit
chosen
Indicates that a venue or performance space includes a designated orchestra pit area for musicians.
-
B.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
C.
hasOrchestraPitCapacity
Indicates the number of people that can be accommodated in the orchestra pit associated with a venue or performance space.
-
D.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
E.
hasSymphonyOrchestra
Indicates that an entity possesses, hosts, or is associated with a symphony orchestra.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4:04 p.m.