Triple
T3844419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Bruges |
E93533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic ecclesiastical territory |
C4228
|
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: Catholic ecclesiastical territory Context triple: [Bishopric of Bruges, instanceOf, Catholic ecclesiastical territory]
-
A.
Roman Catholic ecclesiastical province
A Roman Catholic ecclesiastical province is a territorial grouping of dioceses under the leadership of a metropolitan archbishop, established to coordinate pastoral activity and governance within a defined region of the Church.
-
B.
Roman Catholic diocese
chosen
A Roman Catholic diocese is a territorial division of the Church under the pastoral care and governance of a bishop, responsible for overseeing the spiritual, administrative, and sacramental life of the faithful within its boundaries.
-
C.
Latin Catholic diocese
A Latin Catholic diocese is a territorial ecclesiastical jurisdiction of the Latin Church, governed by a bishop who oversees the pastoral care, administration, and spiritual life of Catholics within its boundaries.
-
D.
Roman Catholic archdiocese
A Roman Catholic archdiocese is a primary ecclesiastical jurisdiction of the Catholic Church, led by an archbishop, that oversees a central territory and often has authority over neighboring dioceses within an ecclesiastical province.
-
E.
group of dioceses
A group of dioceses is an ecclesiastical jurisdiction composed of multiple dioceses united under a higher church authority, such as a province or patriarchate.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:18 p.m.