Triple
T22028657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of England Church Congress |
E544028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican conference |
C2300
|
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 conference Context triple: [Church of England Church Congress, instanceOf, Anglican conference]
-
A.
Anglican episcopal conference
chosen
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.
-
B.
ecumenical conference
An ecumenical conference is a formal gathering of representatives from different Christian denominations, and sometimes other faiths, convened to discuss theological issues, promote unity, and coordinate cooperative action.
-
C.
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.
-
D.
conference of the United Church of Christ
A conference of the United Church of Christ is a regional body that provides governance, support, and coordination for the denomination’s local congregations within a defined geographic area.
-
E.
structure for former Anglicans
A structure for former Anglicans is an organized ecclesial framework or community designed to receive, support, and integrate individuals or groups who have left the Anglican tradition while preserving elements of their spiritual and liturgical heritage.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:24 p.m.