Triple
T5815056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Whitby |
E128963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican ecclesiastical jurisdiction |
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: Anglican ecclesiastical jurisdiction Context triple: [Diocese of Whitby, instanceOf, Anglican ecclesiastical jurisdiction]
-
A.
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.
-
B.
Anglican episcopal conference
An Anglican episcopal conference is a formal assembly of Anglican bishops within a particular region or province that meets to coordinate doctrine, governance, pastoral practice, and common mission for the churches under their oversight.
-
C.
Anglican primatial title
An Anglican primatial title is the official ecclesiastical designation held by the chief bishop or archbishop who serves as the principal leader of an autonomous province within the Anglican Communion.
-
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 church
An Anglican church is a Christian place of worship belonging to the Anglican Communion, characterized by a liturgical tradition that blends elements of Catholic and Reformed practices.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:53 p.m.