Triple
T4958813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Fulham |
E111352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Church of England episcopal office |
C2234
|
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 of England episcopal office Context triple: [Bishop of Fulham, instanceOf, Church of England episcopal office]
-
A.
Anglican clerical position
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.
Anglican bishop
chosen
An Anglican bishop is a senior ordained leader in the Anglican Communion responsible for overseeing a diocese, providing spiritual and administrative guidance, and upholding doctrine and liturgy within the church.
-
C.
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.
-
D.
Anglican archbishop
An Anglican archbishop is a senior bishop within the Anglican Communion who oversees a province or major ecclesiastical jurisdiction, providing spiritual leadership, governance, and representation for the church.
-
E.
Anglican cleric
An Anglican cleric is an ordained minister in the Anglican tradition who leads worship, administers sacraments, provides pastoral care, and upholds the doctrine and discipline of the Anglican Church.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:32 p.m.