Triple
T36039984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Order of Hamburg |
E1042514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran church ordinance |
C34155
|
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 church ordinance Context triple: [Church Order of Hamburg, instanceOf, Lutheran church ordinance]
-
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.
church order
chosen
Church order is the structured system of governance, rules, and practices that organizes the leadership, worship, discipline, and communal life of a Christian church or denomination.
-
C.
Lutheran church office
A Lutheran church office is the administrative center of a Lutheran congregation where pastoral staff and lay workers coordinate worship, ministries, records, and daily church operations.
-
D.
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.
-
E.
work of Lutheran orthodoxy
A work of Lutheran orthodoxy is a theological or doctrinal text produced within the Lutheran tradition, especially between the late 16th and early 18th centuries, that systematically articulates and defends confessional Lutheran beliefs against contemporary challenges.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.