Triple
T10046026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connectional Table |
E207617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church governance body |
C172
|
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: church governance body Context triple: [Connectional Table, instanceOf, church governance body]
-
A.
denominational body
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
B.
church organization
A church organization is a structured religious entity that coordinates worship, spiritual leadership, community services, and administrative functions for a specific faith community.
-
C.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
D.
governing body of the Church of Scotland
The governing body of the Church of Scotland is the General Assembly, a representative council of ministers, elders, and other members that meets to make decisions on doctrine, policy, and administration for the national church.
-
E.
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.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:56 p.m.