Triple
T10962700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statement of Faith (1940) |
E259015
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Church of Canada document |
C10543
|
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: United Church of Canada document Context triple: [Statement of Faith (1940), instanceOf, United Church of Canada document]
-
A.
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.
-
B.
World Council of Churches program area
A World Council of Churches program area is a defined thematic or functional domain within the WCC that coordinates specific initiatives, activities, and resources to advance the council’s ecumenical mission and objectives.
-
C.
Unitarian Universalist church
A Unitarian Universalist church is a liberal religious community that gathers people of diverse beliefs to seek spiritual growth, practice ethical living, and promote social justice without adherence to a fixed creed.
-
D.
church document
chosen
A church document is an official written record or statement produced by a religious institution to communicate doctrine, policy, liturgy, or administrative decisions.
-
E.
World Council of Churches programme area
A World Council of Churches programme area is a defined thematic or functional domain within the WCC that organizes and coordinates specific ecumenical activities, initiatives, and resources to advance the council’s mission and objectives.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:23 p.m.