Triple
T1964826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synod of the Evangelical Church in Germany |
E42664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organ of the Evangelical Church in Germany |
C11943
|
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: organ of the Evangelical Church in Germany Context triple: [Synod of the Evangelical Church in Germany, instanceOf, organ of the Evangelical Church in Germany]
-
A.
Landeskirche
A Landeskirche is a regional Protestant church body in German-speaking countries, historically aligned with specific territories and often functioning as a semi-autonomous public-law institution within the broader national church structure.
-
B.
Landeskirche
A Landeskirche is a regional Protestant church body in German-speaking countries, organized along territorial lines and often historically linked to specific states or regions.
-
C.
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.
-
D.
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 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. chosen
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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.