Triple
T9380322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presbytery of Glasgow |
E225765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing body of the Church of Scotland |
C26048
|
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: governing body of the Church of Scotland Context triple: [Presbytery of Glasgow, instanceOf, governing body of the Church of Scotland]
-
A.
position in the Church of Scotland
A position in the Church of Scotland represents an official role or office within its Presbyterian governance and ministry structure, such as minister, elder, or deacon.
-
B.
Scottish Episcopal diocese
A Scottish Episcopal diocese is a regional jurisdiction of the Scottish Episcopal Church, overseen by a bishop and comprising multiple congregations and clergy within a defined geographic area in Scotland.
-
C.
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.
-
D.
organ of the Church of England
An organ of the Church of England is a formal body or instrument—such as a synod, bishop, or ecclesiastical court—through which the Church carries out its governance, decision-making, and official functions.
-
E.
Presbyterian church
A Presbyterian church is a Christian congregation organized under a representative form of governance by elders, emphasizing Reformed theology, preaching, sacraments, and communal worship.
- F. None of above. chosen
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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:44 p.m.