Triple
T34094608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artistic Director of English National Ballet |
E874390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | executive role in a ballet company |
C38109
|
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: executive role in a ballet company Context triple: [Artistic Director of English National Ballet, instanceOf, executive role in a ballet company]
-
A.
ballet administrator
A ballet administrator oversees the planning, coordination, and management of a ballet company’s operations, including scheduling, budgeting, communications, and support for artistic staff and dancers.
-
B.
position in a performing arts organization
chosen
A position in a performing arts organization represents a defined role or job, encompassing specific responsibilities, authority, and relationships that contribute to the creation, production, or support of artistic performances.
-
C.
position in an opera company
A position in an opera company represents a specific professional role—artistic, technical, or administrative—within the organizational structure that contributes to the planning, production, and performance of operatic works.
-
D.
ballet company co-founder
A ballet company co-founder is an individual who collaboratively establishes and helps shape the artistic vision, organizational structure, and long-term direction of a ballet company.
-
E.
ballet impresario
A ballet impresario is a producer and organizer who finances, manages, and promotes ballet companies, performances, and dancers.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.