Triple
T2800823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussite movement |
E53149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-Reformation movement |
C3445
|
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: pre-Reformation movement Context triple: [Hussite movement, instanceOf, pre-Reformation movement]
-
A.
Christian reform movement
chosen
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.
religious revival movement
A religious revival movement is a collective effort, often marked by intense emotional expression and organized campaigns, aimed at renewing or spreading religious faith and practices within a community or society.
-
C.
millenarian movement
A millenarian movement is a social or religious movement that anticipates an imminent, transformative end to the current world order and the establishment of a radically renewed, often utopian, era.
-
D.
religious conversion movement
A religious conversion movement is a collective effort or organized campaign aimed at persuading individuals or groups to adopt a new religious faith, denomination, or set of spiritual beliefs, often involving structured teachings, rituals, and community support.
-
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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:58 p.m.