Triple
T14427159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregorian Reform |
E357725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church reform 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: church reform movement Context triple: [Gregorian Reform, instanceOf, church reform 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.
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.
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.
-
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.
evangelical movement
A religious and social phenomenon characterized by Protestant Christian groups emphasizing personal conversion, biblical authority, evangelism, and active engagement in shaping culture and public life.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.