Triple
T2148377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Church of Hesse and Nassau |
E47122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Protestant regional church |
C9917
|
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 Protestant regional church Context triple: [Evangelical Church of Hesse and Nassau, instanceOf, United Protestant regional church]
-
A.
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.
-
B.
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.
-
C.
interdenominational Christian church
An interdenominational Christian church is a Christian congregation that welcomes and unites believers from multiple denominational backgrounds, emphasizing shared core beliefs over specific denominational doctrines.
-
D.
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.
-
E.
Presbyterian church
A Presbyterian church is a Christian congregation organized under a representative form of governance by elders, emphasizing Reformed theology, preaching, sacraments, and communal worship.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:44 p.m.