Triple
T8311317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henotikon |
E194596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine religious document |
C11625
|
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 religious document Context triple: [Henotikon, instanceOf, Byzantine religious document]
-
A.
Orthodox Christian treatise
An Orthodox Christian treatise is a formal written work that systematically explains, defends, or reflects upon the doctrines, spiritual life, and liturgical practices of the Eastern Orthodox Church in light of Scripture and Holy Tradition.
-
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.
Gospel book
A Gospel book is a handwritten or printed volume containing the text of one or more of the four canonical Christian Gospels, often richly decorated and used in liturgy and devotion.
-
D.
ecclesiastical document
chosen
An ecclesiastical document is an official written instrument issued or authorized by a church authority that records, communicates, or regulates matters of faith, doctrine, worship, or church governance.
-
E.
collection of ecclesiastical documents
A collection of ecclesiastical documents is an organized set of official church writings—such as decrees, letters, liturgical texts, and doctrinal statements—preserved for reference, governance, and historical record within a religious community.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.