Triple
T22111774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USCCB Region XI |
E546434
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative grouping of dioceses |
C10527
|
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: administrative grouping of dioceses Context triple: [USCCB Region XI, instanceOf, administrative grouping of dioceses]
-
A.
group of dioceses
chosen
A group of dioceses is an ecclesiastical jurisdiction composed of multiple dioceses united under a higher church authority, such as a province or patriarchate.
-
B.
Catholic Church administrative division
A Catholic Church administrative division is a geographically defined ecclesiastical jurisdiction, such as a diocese or parish, overseen by church authorities to organize governance, pastoral care, and liturgical life.
-
C.
subdivision of diocese
A subdivision of diocese is an administrative ecclesiastical unit that forms a smaller territorial or organizational part within a larger diocese.
-
D.
administrative division of the Georgian Orthodox Church
An administrative division of the Georgian Orthodox Church is a territorial ecclesiastical unit, such as a diocese or eparchy, overseen by a bishop and responsible for organizing and governing church life within its boundaries.
-
E.
missionary diocese
A missionary diocese is a territorial ecclesiastical jurisdiction, often in a developing or non-traditional Christian region, established to organize and advance the church’s missionary, pastoral, and evangelizing work under the authority of a bishop or equivalent leader.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.