Triple
T31416556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Mukachevo |
E801407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine Catholic eparchy |
C57516
|
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 Catholic eparchy Context triple: [Eparchy of Mukachevo, instanceOf, Byzantine Catholic eparchy]
-
A.
Byzantine Catholic eparchy
chosen
A Byzantine Catholic eparchy is a territorial jurisdiction of the Eastern Catholic Church, governed by a bishop (eparch) who oversees the pastoral, liturgical, and administrative life of Byzantine-rite faithful in communion with the Pope.
-
B.
Ukrainian Greek Catholic archeparchy
A Ukrainian Greek Catholic archeparchy is a principal ecclesiastical jurisdiction of the Ukrainian Greek Catholic Church, headed by an archeparch and overseeing multiple eparchies within a defined territory.
-
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.
Metropolitan archeparchy
A metropolitan archeparchy is a principal Eastern Catholic ecclesiastical jurisdiction, headed by a metropolitan archbishop, that presides over its own territory and often has suffragan eparchies under its authority.
-
E.
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.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:44 p.m.