Triple
T9514661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon Theologian of Leicester Cathedral |
E229492
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | position in the Church of England |
C6848
|
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: position in the Church of England Context triple: [Canon Theologian of Leicester Cathedral, instanceOf, position in the Church of England]
-
A.
Anglican clerical position
chosen
An Anglican clerical position is an official role within the Anglican Church’s ordained or licensed ministry structure, encompassing responsibilities for worship, pastoral care, administration, and spiritual leadership in a parish or wider ecclesiastical jurisdiction.
-
B.
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.
-
C.
policy of the Church of England
The policy of the Church of England is the body of principles, rules, and official positions that guide its governance, doctrine, worship, and public engagement.
-
D.
Church of England benefice
A Church of England benefice is an ecclesiastical office or group of parishes under the pastoral care of a single incumbent (such as a rector or vicar), who is entitled to receive its associated income and responsibilities.
-
E.
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.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:58 p.m.