Triple
T29547088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauhaus stage experiments |
E749658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | experimental theatre |
C16475
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: experimental theatre Context triple: [Bauhaus stage experiments, instanceOf, experimental theatre]
-
A.
experimental theatre company
chosen
An experimental theatre company is a performance collective that creates innovative, boundary-pushing stage works by exploring unconventional narratives, forms, and audience relationships.
-
B.
experimental opera
Experimental opera is a boundary-pushing form of musical theater that reimagines traditional operatic elements—such as narrative, vocal technique, staging, and instrumentation—through unconventional structures, multimedia integration, and innovative performance practices.
-
C.
fringe theatre
Fringe theatre is a form of experimental, low-budget, and often unconventional performance art produced outside the mainstream commercial theatre system, typically emphasizing artistic innovation and risk-taking.
-
D.
epic theatre work
An epic theatre work is a dramatic piece designed to provoke critical reflection and social awareness in the audience through techniques that disrupt emotional immersion, such as narration, direct address, and visible theatrical devices.
-
E.
experimental music act
An experimental music act is a musical project or group that deliberately challenges conventional structures, sounds, and performance practices to explore new, unconventional, or avant-garde sonic possibilities.
- F. None of above.
Provenance (1 batch)
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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:08 p.m.