Triple
T24025424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oliver Morosco |
E594942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American theatre manager |
C2388
|
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: American theatre manager Context triple: [Oliver Morosco, instanceOf, American theatre manager]
-
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.
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.
-
C.
theatre executive
A theatre executive is a senior manager responsible for overseeing the artistic vision, financial health, and operational management of a theatre organization or venue.
-
D.
American entertainment manager
An American entertainment manager is a professional who oversees and advances the careers of artists and performers in the United States by handling business negotiations, strategic planning, and day-to-day professional affairs.
-
E.
theatrical producer
chosen
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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:53 p.m.