Triple
T23067272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prebendary of Salisbury Cathedral |
E575081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical position |
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: ecclesiastical position Context triple: [Prebendary of Salisbury Cathedral, instanceOf, ecclesiastical position]
-
A.
ecclesiastical office-holding body
An ecclesiastical office-holding body is a formally constituted group within a religious organization that collectively holds, administers, or oversees specific church offices, duties, or authorities.
-
B.
bishopric office
A bishopric office is an administrative and pastoral center where a bishop and their staff conduct the governance, coordination, and support of ecclesiastical activities within a diocese or similar church jurisdiction.
-
C.
ecclesiastical authority
Ecclesiastical authority is the recognized power and jurisdiction exercised by religious officials or institutions to govern doctrine, discipline, and practice within a faith community.
-
D.
Christian religious office
A Christian religious office is an institutional role or position within a Christian church or denomination, endowed with specific spiritual, liturgical, and administrative responsibilities and authority.
-
E.
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.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:55 p.m.