Triple
T1949439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fundamentalist–modernist controversy |
E42126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict within American Protestantism |
C3648
|
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: conflict within American Protestantism Context triple: [Fundamentalist–modernist controversy, instanceOf, conflict within American Protestantism]
-
A.
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.
-
B.
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.
-
C.
religious controversy
chosen
Religious controversy is a sustained conflict or debate arising from differing beliefs, doctrines, practices, or interpretations within or between religious traditions.
-
D.
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.
-
E.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.