Triple
T2664362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shubert Organization |
E55599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theatrical producing company |
C10471
|
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: theatrical producing company Context triple: [Shubert Organization, instanceOf, theatrical producing 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.
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.
-
C.
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.
-
D.
commercial production company
A commercial production company is a business entity that specializes in planning, filming, and producing video advertisements and branded content for clients across various media platforms.
-
E.
production company
A production company is a business entity that develops, finances, and manages the creation of media content such as films, television shows, music, or digital productions.
- F. None of above. chosen
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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.