Triple
T4944226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican authorities |
E111007
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican ecclesiastical structure |
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 ecclesiastical structure Context triple: [Anglican authorities, instanceOf, Anglican ecclesiastical structure]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
institution of the Episcopal Church
An institution of the Episcopal Church is an organized body, such as a parish, diocese, school, or agency, that operates under the authority, doctrine, and governance structures of the Episcopal Church to carry out its religious, educational, or charitable mission.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:31 p.m.