Triple
T9178248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformation of the Church in Strasbourg |
E220255
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church reform program |
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: church reform program Context triple: [Reformation of the Church in Strasbourg, instanceOf, church reform program]
-
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.
organ reform movement
The organ reform movement was a 20th-century initiative in organ building and performance that sought to revive historical principles of design, sound, and technique, particularly those of Baroque instruments, in reaction against the symphonic and romantic organ traditions.
-
C.
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.
-
D.
church reformer
A church reformer is an individual who seeks to change, purify, or revitalize religious institutions, doctrines, or practices from within a particular faith tradition.
-
E.
religious policy change
A religious policy change is a deliberate alteration in the rules, doctrines, or practices governing religious institutions or state-religion relations, typically enacted to address evolving social, political, or cultural conditions.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:23 p.m.