Triple
T24168279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Nekresi (historical) |
E599054
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian eparchy |
C17218
|
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: Christian eparchy Context triple: [Eparchy of Nekresi (historical), instanceOf, Christian eparchy]
-
A.
Christian diocese
chosen
A Christian diocese is a geographic ecclesiastical district under the pastoral care and administrative authority of a bishop within a particular Christian denomination.
-
B.
Syro-Malankara Catholic eparchy
A Syro-Malankara Catholic eparchy is a territorial jurisdiction of the Syro-Malankara Catholic Church, headed by a bishop, responsible for the pastoral care, administration, and liturgical life of the faithful within its defined region.
-
C.
Maronite Catholic eparchy
A Maronite Catholic eparchy is a territorial jurisdiction of the Maronite Church, governed by a bishop (eparch) who oversees the pastoral care, administration, and liturgical life of Maronite Catholics within its boundaries.
-
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.
Oriental Orthodox patriarchate
An Oriental Orthodox patriarchate is a highest-ranking ecclesiastical jurisdiction led by a patriarch within the Oriental Orthodox communion, overseeing the spiritual, administrative, and liturgical life of its faithful in a particular region or tradition.
- 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:33 p.m.