Triple
T4396244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Evangelical Synod of the Northwest |
E99494
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran and Reformed church body |
C8679
|
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: Lutheran and Reformed church body Context triple: [German Evangelical Synod of the Northwest, instanceOf, Lutheran and Reformed church body]
-
A.
Lutheran church
A Lutheran church is a Christian congregation or building that follows the teachings of Martin Luther and the Lutheran Confessions, emphasizing salvation by grace through faith, the authority of Scripture, and liturgical worship.
-
B.
Protestant regional church
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.
-
C.
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.
-
D.
United Protestant regional church
chosen
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a shared governance, worship life, and mission.
-
E.
United Protestant regional church
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a common organizational and theological framework.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:20 p.m.