Triple
T31251910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House/Lights |
E796846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | experimental theater production |
C58989
|
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 theater production Context triple: [House/Lights, instanceOf, experimental theater production]
-
A.
experimental theater piece
chosen
An experimental theater piece is a live performance work that deliberately challenges conventional narrative, staging, and audience expectations through innovative, unconventional, or interdisciplinary theatrical techniques.
-
B.
experimental theatre company
An experimental theatre company is a performance collective that creates innovative, boundary-pushing stage works by exploring unconventional narratives, forms, and audience relationships.
-
C.
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.
-
D.
theater workshop
A theater workshop is a structured, collaborative learning environment where participants explore and develop performance skills through exercises, improvisations, and guided practice.
-
E.
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.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:11 p.m.