Triple
T17417861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Diocese of Turku |
E423530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Latin-rite ecclesiastical jurisdiction |
C4229
|
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: medieval Latin-rite ecclesiastical jurisdiction Context triple: [Catholic Diocese of Turku, instanceOf, medieval Latin-rite ecclesiastical jurisdiction]
-
A.
ecclesiastical jurisdiction
An ecclesiastical jurisdiction is a defined territorial or personal area of authority within a religious organization, governed by church law and overseen by designated clerical leaders.
-
B.
Roman Catholic territorial jurisdiction
A Roman Catholic territorial jurisdiction is an ecclesiastical region, such as a diocese or archdiocese, over which a bishop or equivalent church authority exercises pastoral and administrative governance.
-
C.
ecclesiastical court system
An ecclesiastical court system is a hierarchical network of church-run tribunals that adjudicate matters of doctrine, discipline, and religious law within a particular faith community.
-
D.
Latin Catholic diocese
chosen
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.
ecclesiastical authority
Ecclesiastical authority is the recognized power and jurisdiction exercised by religious officials or institutions to govern doctrine, discipline, and practice within a faith community.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:46 a.m.