Triple
T26017949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auchterarder case |
E647072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical law case |
C30064
|
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: ecclesiastical law case Context triple: [Auchterarder case, instanceOf, ecclesiastical law case]
-
A.
ecclesiastical law code
An ecclesiastical law code is a systematic collection of rules and regulations issued by a religious authority to govern the doctrine, discipline, and organizational life of a church or religious community.
-
B.
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.
-
C.
ecclesiastical court system
chosen
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.
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.
-
E.
canon law provision
A canon law provision is a specific, authoritative rule or norm established by a competent ecclesiastical authority to regulate conduct, governance, and doctrine within the Church’s legal system.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:03 a.m.