Triple
T2309994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Kenwright |
E51930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British theatre producer |
C2838
|
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: British theatre producer Context triple: [Bill Kenwright, instanceOf, British theatre producer]
-
A.
American theatre producer
An American theatre producer is a professional who oversees the financing, development, and management of theatrical productions in the United States, coordinating creative, logistical, and business aspects to bring stage works to audiences.
-
B.
theatre producer
chosen
A theatre producer is the individual responsible for overseeing and coordinating all financial, logistical, and organizational aspects of a stage production, from securing rights and funding to assembling the creative team and managing the show’s run.
-
C.
Broadway theater producer
A Broadway theater producer is a professional who secures financing, assembles creative and technical teams, oversees production logistics, and manages the business and artistic aspects of bringing a stage show to Broadway audiences.
-
D.
theatrical producer
A theatrical producer is the individual responsible for overseeing and coordinating all financial, logistical, and creative aspects of a stage production, from development and funding through casting, rehearsals, and performance.
-
E.
theatre director
A theatre director is the creative leader who interprets a script and coordinates actors, designers, and technical staff to shape the overall vision and execution of a stage production.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:49 p.m.