Triple
T29321478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilles Binchois |
E743525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Burgundian School composer |
C18690
|
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: Burgundian School composer Context triple: [Gilles Binchois, instanceOf, Burgundian School composer]
-
A.
Franco-Flemish composer
A Franco-Flemish composer is a Renaissance-era musician from the region spanning modern northern France, Belgium, and the Netherlands, known for sophisticated polyphonic vocal music that significantly shaped European musical development.
-
B.
medieval composer
chosen
A medieval composer is a musician from the Middle Ages who created primarily vocal and liturgical music, often for the Church or courtly settings, using early notational systems and modal frameworks.
-
C.
English Baroque composer
An English Baroque composer is a musician from England active roughly between 1600 and 1750 who created vocal and instrumental works characterized by ornate melodies, expressive harmonies, and often sacred or courtly functions within the Baroque style.
-
D.
Swiss composer
A Swiss composer is a musician from Switzerland who creates original musical works, often reflecting the country’s diverse cultural traditions and contemporary artistic influences.
-
E.
Baroque musician
A Baroque musician is a performer or composer active in the Baroque period (c. 1600–1750), characterized by ornate musical expression, use of basso continuo, and adherence to stylistic conventions of contrast, ornamentation, and affect.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:23 p.m.