Triple
T4798064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deanery of Westminster (St Margaret) and St John |
E106761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Church of England administrative unit |
C15231
|
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 administrative unit Context triple: [Deanery of Westminster (St Margaret) and St John, instanceOf, Church of England administrative unit]
-
A.
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.
-
B.
Church of England deanery
chosen
A Church of England deanery is a local administrative division within a diocese, comprising a group of parishes overseen by a rural or area dean to coordinate ministry and church activities.
-
C.
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.
-
D.
Anglican Communion institution
An Anglican Communion institution is an organization, body, or entity formally associated with or serving the global fellowship of autonomous Anglican churches, supporting their shared mission, governance, worship, or theological identity.
-
E.
Anglican episcopal see
An Anglican episcopal see is the geographical area of jurisdiction and the associated office of a bishop within the Anglican Communion.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:22 p.m.