Triple
T24842644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysanthine notation |
E621656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine musical notation |
C21297
|
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: Byzantine musical notation Context triple: [Chrysanthine notation, instanceOf, Byzantine musical notation]
-
A.
Byzantine chant notation
chosen
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.
-
B.
Hindustani music notation
Hindustani music notation is a symbolic system used to represent the pitches, rhythms, ornamentations, and structures of North Indian classical music, typically through sargam syllables, time cycles (tala), and other performance directives.
-
C.
Hebrew cantillation marks
Hebrew cantillation marks are a system of symbols added to biblical texts that indicate melodic chanting patterns, syntactic breaks, and accentuation for liturgical reading.
-
D.
Glagolitic manuscript
A Glagolitic manuscript is a handwritten document produced using the Glagolitic alphabet, one of the earliest Slavic scripts, typically preserving religious, liturgical, or legal texts from the medieval Slavic cultural sphere.
-
E.
Byzantine ceremonial manual
A Byzantine ceremonial manual is a prescriptive guide detailing the rituals, protocols, and symbolic actions governing imperial, ecclesiastical, and court ceremonies in the Byzantine Empire.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:19 a.m.