Triple
T19131085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Being as Communion |
E468315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | work of Orthodox Christian theology |
C5743
|
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: work of Orthodox Christian theology Context triple: [Being as Communion, instanceOf, work of Orthodox Christian theology]
-
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.
Eastern Orthodox doctrine
Eastern Orthodox doctrine is the body of theological teachings and spiritual practices of the Eastern Orthodox Church, emphasizing the continuity of apostolic tradition, the authority of the Ecumenical Councils, and the transformative process of theosis.
-
C.
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.
-
D.
Eastern Orthodox reference work
A comprehensive resource that systematically presents, explains, and documents the beliefs, practices, history, and canonical texts of the Eastern Orthodox Church.
-
E.
theological work
chosen
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:05 p.m.