Triple
T37628942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old School–New School Presbyterian controversies |
E936287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century religious controversy |
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: 19th-century religious controversy Context triple: [Old School–New School Presbyterian controversies, instanceOf, 19th-century religious controversy]
-
A.
19th-century controversy
A 19th-century controversy is a significant public dispute or prolonged debate during the 1800s, often involving social, political, scientific, or religious issues that shaped contemporary thought and policy.
-
B.
19th-century religion
19th-century religion encompasses the diverse religious movements, revivals, reforms, and conflicts that shaped spiritual life and institutions worldwide during the 1800s amid rapid social, political, and scientific change.
-
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.
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.
-
E.
19th-century conflict
A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.