Triple
T22387255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Constantinople 1341 |
E553426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine synod |
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: Byzantine synod Context triple: [Council of Constantinople 1341, instanceOf, Byzantine synod]
-
A.
Eastern Church synod
An Eastern Church synod is an official assembly of bishops and other ecclesiastical leaders within an Eastern Christian tradition convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
B.
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.
-
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.
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.
-
E.
Byzantine reform movement
The Byzantine reform movement was a series of religious, administrative, and military initiatives within the Byzantine Empire aimed at strengthening imperial authority, purifying religious practice, and restoring social and economic stability in response to internal decay and external threats.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.