Triple
T4005972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Communion networks |
E89526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international ecclesial network |
C7115
|
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: international ecclesial network Context triple: [Anglican Communion networks, instanceOf, international ecclesial network]
-
A.
evangelical network
An evangelical network is a loosely organized yet interconnected group of individuals, churches, and organizations that share and promote evangelical Christian beliefs, resources, and activities across various social, cultural, and media channels.
-
B.
ecumenical organization
An ecumenical organization is a group or body that promotes cooperation, dialogue, and unity among different Christian denominations while respecting their distinct traditions and beliefs.
-
C.
ecumenical dialogue commission
An ecumenical dialogue commission is a formal body composed of representatives from different Christian traditions tasked with fostering theological discussion, mutual understanding, and cooperative initiatives toward greater church unity.
-
D.
religious network
chosen
A religious network is a structured system of individuals, groups, and institutions connected by shared beliefs, practices, and organizational ties that facilitate the spread and maintenance of a religious tradition.
-
E.
communion of churches
A communion of churches is an association of autonomous Christian churches that recognize each other’s ministries and sacraments, and share a common faith, doctrine, and ecclesial life while retaining their own governance structures.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:34 p.m.