Triple
T5674631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autonomy and the Means by Which it is Proclaimed |
E125055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | official document of the Orthodox Church |
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: official document of the Orthodox Church Context triple: [Autonomy and the Means by Which it is Proclaimed, instanceOf, official document of the Orthodox Church]
-
A.
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.
-
B.
organ of the Russian Orthodox Church
An organ of the Russian Orthodox Church is a formal institutional body or administrative unit within the Church that carries out specific religious, governance, or organizational functions under its canonical authority.
-
C.
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.
-
D.
Catholic Church document
A Catholic Church document is an official written text issued or approved by Church authority that communicates, clarifies, or governs matters of faith, morals, liturgy, or discipline.
-
E.
organ of the Bulgarian Orthodox Church
An organ of the Bulgarian Orthodox Church is an official institutional body or administrative unit that performs specific religious, governance, or support functions within the Church’s hierarchical structure.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:43 p.m.