Triple
T2535674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nederlander Organization |
E56262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theatre-owning company |
C5721
|
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: theatre-owning company Context triple: [Nederlander Organization, instanceOf, theatre-owning company]
-
A.
regional theater company
A regional theater company is a professional performing arts organization that produces and presents live theatrical productions for a specific geographic area, often featuring local talent and serving as a cultural hub for its community.
-
B.
theater owner
chosen
A theater owner is an individual or entity that possesses and manages a performance venue, overseeing its operations, programming, finances, and maintenance.
-
C.
theatre industry organization
A theatre industry organization is an entity that supports, represents, or coordinates the activities of theatres and theatre professionals through advocacy, networking, resource sharing, and industry standards.
-
D.
theatre producer
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.
-
E.
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.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:47 p.m.