Triple
T2430352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instruments of Communion of the Anglican Communion |
E52827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical governance structure |
C9797
|
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 governance structure Context triple: [Instruments of Communion of the Anglican Communion, instanceOf, ecclesiastical governance structure]
-
A.
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.
-
B.
ecclesiastical institution
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
-
C.
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.
-
D.
form of church polity
chosen
A form of church polity is a conceptual structure that defines how authority, decision-making, and governance are organized and exercised within a Christian church or denomination.
-
E.
form of church polity
A form of church polity is a specific organizational structure and system of governance that defines how authority, decision-making, and leadership are distributed and exercised within a Christian church or denomination.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:43 p.m.