Triple
T31641536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Archeparchy of Pittsburgh |
E807470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metropolitan archeparchy |
C34038
|
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: metropolitan archeparchy Context triple: [Metropolitan Archeparchy of Pittsburgh, instanceOf, metropolitan archeparchy]
-
A.
Metropolitan archeparchy
chosen
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.
-
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.
Byzantine Catholic eparchy
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.
-
D.
metropolitan archbishop
A metropolitan archbishop is a senior bishop who presides over an ecclesiastical province, holding limited authority over the suffragan dioceses and their bishops within that region.
-
E.
major archeparchy
A major archeparchy is a principal ecclesiastical jurisdiction in certain Eastern Catholic Churches, headed by a major archbishop and equivalent in status to a patriarchate within that church’s hierarchy.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:49 p.m.