Triple
T22878804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XII Concerti grossi, con duoi violini e violoncello di concertino obligato, e duoi altri violini, viola e basso di concerto grosso |
E567399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | set of concerti grossi |
C37566
|
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: set of concerti grossi Context triple: [XII Concerti grossi, con duoi violini e violoncello di concertino obligato, e duoi altri violini, viola e basso di concerto grosso, instanceOf, set of concerti grossi]
-
A.
concerto grosso
chosen
A concerto grosso is a Baroque musical form in which a small group of solo instruments (concertino) alternates and contrasts with a larger ensemble (ripieno or tutti).
-
B.
cello concerto
A cello concerto is a musical composition, typically in three movements, that features a solo cello accompanied by an orchestra, showcasing the instrument’s expressive and technical capabilities.
-
C.
harpsichord concerto
A harpsichord concerto is a musical composition, typically from the Baroque era, featuring a harpsichord as the solo instrument accompanied by an orchestra in a multi-movement structure.
-
D.
viola concerto
A viola concerto is a musical composition, typically in three movements, that features the viola as a solo instrument accompanied by an orchestra.
-
E.
violin concerto
A violin concerto is a musical composition, typically in three movements, that features a solo violin accompanied by an orchestra, showcasing the instrument’s expressive and technical capabilities.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:39 p.m.