Triple
T36039985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Order of Hamburg |
E1042514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Reformation-era church ordinance |
C22446
|
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: Reformation-era church ordinance Context triple: [Church Order of Hamburg, instanceOf, Reformation-era church ordinance]
-
A.
Protestant reform measure
chosen
A Protestant reform measure is a specific policy, decree, or action implemented to align religious, political, or social practices with Protestant theological principles and church governance.
-
B.
Reformed confessional status
Reformed confessional status is the recognized standing of a church, minister, or individual as formally subscribing to and being governed by a specific historic Reformed confession of faith.
-
C.
Puritan practice
Puritan practice is the disciplined, community-oriented application of strict moral, religious, and social codes derived from a literal interpretation of Scripture, shaping daily life, worship, and governance.
-
D.
16th-century theological document
A 16th-century theological document is a written work from the 1500s that articulates, debates, or codifies religious doctrines, beliefs, or practices within the historical context of Reformation-era Christianity.
-
E.
Tudor-era reform
Tudor-era reform refers to the series of political, religious, and administrative changes in 16th-century England, particularly under Henry VIII and Elizabeth I, that redefined the monarchy’s power, broke from the Roman Catholic Church, and laid foundations for the modern English state.
- 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.