Triple
T14644705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Schwerin |
E343816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical bishopric |
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 bishopric Context triple: [Diocese of Schwerin, instanceOf, historical bishopric]
-
A.
bishopric office
A bishopric office is an administrative and pastoral center where a bishop and their staff conduct the governance, coordination, and support of ecclesiastical activities within a diocese or similar church jurisdiction.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
ancient patriarchate
An ancient patriarchate is a senior episcopal jurisdiction in early Christianity, historically led by a patriarch who held preeminent authority over a major Christian center and its surrounding territories.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.