Triple
T24645968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberlin Baroque Ensemble |
E610110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historically informed performance group |
C1040
|
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: historically informed performance group Context triple: [Oberlin Baroque Ensemble, instanceOf, historically informed performance group]
-
A.
performer of early music
A performer of early music is a musician who specializes in interpreting and presenting music from the Medieval, Renaissance, and Baroque periods, often using historical instruments and performance practices.
-
B.
contemporary performance practice
Contemporary performance practice is the evolving set of methods, theories, and creative strategies that artists use to devise, stage, and critically engage with live and mediated performance in today’s cultural, technological, and social contexts.
-
C.
musical ensemble
chosen
A musical ensemble is a group of musicians who perform together, typically coordinated under a shared arrangement or purpose, to create a unified musical work.
-
D.
group of orchestras
A group of orchestras is a collection of multiple orchestral ensembles that are organized or associated together, often for collaborative performances, shared administration, or joint artistic initiatives.
-
E.
baroque orchestra
A baroque orchestra is an ensemble of musicians performing 17th- and early 18th-century music on period or historically informed instruments, typically featuring strings, continuo, and a small group of winds and brass.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:33 a.m.