Triple
T4626933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Leuven |
E101120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval ecclesiastical jurisdiction |
C575
|
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 ecclesiastical jurisdiction Context triple: [Bishopric of Leuven, instanceOf, medieval ecclesiastical jurisdiction]
-
A.
ecclesiastical jurisdiction
chosen
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.
medieval law
Medieval law is the body of legal customs, codes, and practices that governed social, economic, and political life in Europe during the Middle Ages, blending local traditions, feudal obligations, royal decrees, and canon (church) law.
-
C.
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.
-
D.
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.
-
E.
medieval legislation
Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:13 p.m.