Triple
T929548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peasants’ War |
E20059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Protestant Reformation |
C1474
|
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: event in the Protestant Reformation Context triple: [Peasants’ War, instanceOf, event in the Protestant Reformation]
-
A.
Christian reform movement
A Christian reform movement is a religious initiative within Christianity aimed at renewing faith, correcting perceived doctrinal or moral errors, and transforming church practices or social structures in light of biblical principles.
-
B.
event in church history
chosen
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
C.
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.
-
D.
New Testament event
A New Testament event is a significant occurrence or episode described in the New Testament writings that contributes to the narrative, theology, or historical context of early Christianity.
-
E.
Puritan controversy
A Puritan controversy is a historical or theological dispute arising within Puritan communities over matters of doctrine, church governance, or moral practice that challenged established religious authority and norms.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.