Triple
T21913634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micrologus |
E541126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval music treatise |
C45507
|
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: medieval music treatise Context triple: [Micrologus, instanceOf, medieval music treatise]
-
A.
medieval music style
A medieval music style is a historically rooted musical idiom characterized by modal melodies, monophonic or early polyphonic textures, and performance practices typical of European music from roughly the 5th to the 15th century.
-
B.
medieval composer
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.
medieval harp
A medieval harp is a stringed musical instrument with a triangular frame and gut or wire strings, played by plucking to accompany songs, poetry, and courtly or religious performances in the Middle Ages.
-
D.
Byzantine chant notation
Byzantine chant notation is a medieval and later musical notation system used in the Eastern Orthodox Church to record and transmit the melodic formulas and modal structures of Byzantine chant through specialized neumes and symbols.
-
E.
Renaissance music piece
A Renaissance music piece is a vocal or instrumental composition from roughly the 15th to early 17th centuries, characterized by modal harmony, imitative polyphony, and a balance between sacred and secular forms.
- F. None of above. chosen
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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:42 p.m.