Triple
T10352625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurich church |
E243916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant ecclesiastical body |
C9317
|
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: Protestant ecclesiastical body Context triple: [Zurich church, instanceOf, Protestant ecclesiastical body]
-
A.
Christian ecumenical body
A Christian ecumenical body is an organized association of churches or Christian communities from different traditions that collaborates to promote unity, shared witness, and common action in faith and practice.
-
B.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
-
C.
Anglican Communion body
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.
Protestant regional church
chosen
A Protestant regional church is a territorially organized ecclesiastical body that unites Protestant congregations within a specific geographic area under shared governance, doctrine, and administrative structures.
-
E.
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.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:57 a.m.