Triple
T19492169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedalion |
E487678
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greek Orthodox canonical collection |
C16843
|
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: Greek Orthodox canonical collection Context triple: [Pedalion, instanceOf, Greek Orthodox canonical collection]
-
A.
Ethiopian Orthodox scripture
Ethiopian Orthodox scripture is the canon of sacred writings used by the Ethiopian Orthodox Tewahedo Church, encompassing an expansive collection of biblical and extra-biblical texts preserved in Geʽez that guide its theology, liturgy, and spiritual life.
-
B.
Orthodox Christian hymnographic work
An Orthodox Christian hymnographic work is a liturgical or devotional text set to chant or song that poetically expresses and interprets the theology, feasts, saints, and spiritual life of the Orthodox Church.
-
C.
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.
-
D.
Eastern Orthodox reference work
chosen
A comprehensive resource that systematically presents, explains, and documents the beliefs, practices, history, and canonical texts of the Eastern Orthodox Church.
-
E.
patristic text collection
A patristic text collection is an organized compilation of writings by the early Christian Church Fathers, typically gathered for study, reference, or theological analysis.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.