Triple
T32904094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Lutheran Church in Monaco |
E841687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran congregation |
C6216
|
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 congregation Context triple: [Evangelical Lutheran Church in Monaco, instanceOf, Lutheran congregation]
-
A.
Lutheran church
chosen
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 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.
Lutheran diocese
A Lutheran diocese is an administrative and ecclesiastical district of the Lutheran Church, overseen by a bishop and comprising multiple congregations within a defined geographic area.
-
D.
Evangelische Kirchengemeinde
An Evangelische Kirchengemeinde is a local Protestant church congregation, typically within the German-speaking context, that organizes worship, pastoral care, community activities, and religious education for its members and surrounding community.
-
E.
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.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.