Triple
T5823281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapter of Westminster Abbey |
E129160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican church body |
C2239
|
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 church body Context triple: [Chapter of Westminster Abbey, instanceOf, Anglican church body]
-
A.
Anglican Communion body
chosen
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.
-
B.
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.
-
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.
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.
-
E.
Anglican religious community
An Anglican religious community is a group of men or women within the Anglican tradition who live under a common rule of life, sharing prayer, worship, and service in a vowed or committed communal setting.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:53 p.m.