Triple
T25678934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican dioceses of northern India |
E643883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of Anglican dioceses |
C10527
|
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: group of Anglican dioceses Context triple: [Anglican dioceses of northern India, instanceOf, group of Anglican dioceses]
-
A.
Anglican dioceses
Anglican dioceses are regional ecclesiastical jurisdictions within the Anglican Communion, each overseen by a bishop who provides spiritual leadership, governance, and pastoral care to the churches and clergy in that area.
-
B.
group of dioceses
chosen
A group of dioceses is an ecclesiastical jurisdiction composed of multiple dioceses united under a higher church authority, such as a province or patriarchate.
-
C.
governing body of the Anglican Communion
The governing body of the Anglican Communion is the collective international authority—principally expressed through the Lambeth Conference, the Anglican Consultative Council, and the Primates’ Meeting—that guides doctrine, mission, and policy across its autonomous member churches.
-
D.
Anglican Communion body
An Anglican Communion body is an organizational entity, such as a church, council, or commission, that participates in and helps govern the worldwide fellowship of Anglican churches.
-
E.
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.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 7:44 p.m.