Triple
T5631856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curia of the Abbot Primate |
E147851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical administrative body |
C2176
|
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 administrative body Context triple: [Curia of the Abbot Primate, instanceOf, ecclesiastical administrative body]
-
A.
ecclesiastical institution
chosen
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.
-
B.
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.
-
C.
ecumenical organization
An ecumenical organization is a group or body that promotes cooperation, dialogue, and unity among different Christian denominations while respecting their distinct traditions and beliefs.
-
D.
governing body of the Anglican Communion
The governing body of the Anglican Communion is the collective international authority—principally expressed through the Lambeth Conference, the Anglican Consultative Council, and the Primates’ Meeting—that guides doctrine, mission, and policy across its autonomous member churches.
-
E.
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.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:40 p.m.