Triple
T5674377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy and Great Council |
E125050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Orthodox council |
C1457
|
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: Eastern Orthodox council Context triple: [Holy and Great Council, instanceOf, Eastern Orthodox council]
-
A.
ecclesiastical council
chosen
An ecclesiastical council is a formal assembly of church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
B.
Eastern Orthodox church
An Eastern Orthodox church is a Christian place of worship characterized by its adherence to Eastern Orthodox theology and liturgy, often featuring domes, icons, and a richly decorated interior focused on the Divine Liturgy.
-
C.
Eastern Christian church
An Eastern Christian church is a Christian community or building belonging to the Eastern Christian traditions (such as Eastern Orthodox, Oriental Orthodox, or Eastern Catholic), characterized by distinct liturgical rites, theology, and ecclesiastical heritage rooted in the Christian East.
-
D.
Byzantine Rite Church
A Byzantine Rite Church is a Christian church that follows the liturgical, theological, and spiritual traditions of the Byzantine rite, characterized by its Eastern Christian worship, iconography, and ecclesiastical customs.
-
E.
set of ecumenical councils
A set of ecumenical councils is a collection of formally convened universal church assemblies recognized for authoritatively defining doctrine, discipline, and responses to major theological or ecclesial controversies.
- 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.