Triple
T10289477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of the Evangelical Church of Kurhessen-Waldeck |
E241323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant church office |
C6971
|
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 church office Context triple: [Bishop of the Evangelical Church of Kurhessen-Waldeck, instanceOf, Protestant church office]
-
A.
Protestant minister
A Protestant minister is a Christian clergy member who leads worship, preaches, provides pastoral care, and administers religious rites within a Protestant congregation or community.
-
B.
Christian religious office
chosen
A Christian religious office is an institutional role or position within a Christian church or denomination, endowed with specific spiritual, liturgical, and administrative responsibilities and authority.
-
C.
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.
-
D.
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.
-
E.
Reformed church building
A Reformed church building is a Christian worship structure designed and used by congregations within the Reformed (Calvinist) tradition, typically characterized by simple, unadorned architecture that emphasizes preaching and congregational gathering.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:41 a.m.