Triple
T4730185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Roermond |
E104985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical diocese |
C15374
|
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: historical diocese Context triple: [Bishopric of Roermond, instanceOf, historical diocese]
-
A.
former Catholic diocese
chosen
A former Catholic diocese is an ecclesiastical jurisdiction of the Catholic Church that once functioned as a territorial diocese but has since been suppressed, merged, or otherwise ceased to exist in its original administrative form.
-
B.
Roman Catholic diocese
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.
historic parish
A historic parish is a former ecclesiastical or civil territorial unit, typically centered around a church, whose boundaries and institutions reflect the administrative and social organization of a past period.
-
D.
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.
-
E.
medieval Scottish bishopric
A medieval Scottish bishopric was an ecclesiastical jurisdiction headed by a bishop, overseeing the spiritual, administrative, and often political affairs of the Church within a defined region of Scotland during the Middle Ages.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:19 p.m.