Triple
T9844521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anaphora of St. John Chrysostom |
E239305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine anaphora |
C9614
|
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 anaphora Context triple: [Anaphora of St. John Chrysostom, instanceOf, Byzantine anaphora]
-
A.
Byzantine supplicatory canon
A Byzantine supplicatory canon is a structured liturgical hymn composed of multiple odes, chanted in the Eastern Christian tradition to implore divine mercy, aid, or intercession, often addressed to Christ, the Theotokos, or specific saints.
-
B.
Byzantine theme
A Byzantine theme was a military-administrative district of the Byzantine Empire, governed by a strategos who oversaw both civil administration and regional defense.
-
C.
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.
-
D.
Byzantine reform movement
The Byzantine reform movement was a series of religious, administrative, and military initiatives within the Byzantine Empire aimed at strengthening imperial authority, purifying religious practice, and restoring social and economic stability in response to internal decay and external threats.
-
E.
anaphora
chosen
Anaphora is a rhetorical and linguistic device in which a word or group of words is deliberately repeated at the beginning of successive clauses, sentences, or lines to create emphasis, rhythm, or cohesion.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:33 p.m.