Triple
T6646026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingswood and South Gloucestershire Deanery |
E150701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical administrative unit |
C575
|
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 administrative unit Context triple: [Kingswood and South Gloucestershire Deanery, instanceOf, ecclesiastical administrative unit]
-
A.
ecclesiastical institution
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
-
B.
ecclesiastical jurisdiction
chosen
An ecclesiastical jurisdiction is a defined territorial or personal area of authority within a religious organization, governed by church law and overseen by designated clerical leaders.
-
C.
group of dioceses
A group of dioceses is an ecclesiastical jurisdiction composed of multiple dioceses united under a higher church authority, such as a province or patriarchate.
-
D.
administrative unit of the Seventh-day Adventist Church
An administrative unit of the Seventh-day Adventist Church is an organizational entity, such as a conference, mission, union, or division, responsible for overseeing and coordinating the church’s activities, governance, and ministries within a defined geographic territory.
-
E.
ecclesiastical state
An ecclesiastical state is a political entity in which the government is directly controlled by religious authorities, often with a church leader serving as the head of state.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2 p.m.