Triple
T31958618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Unitarianism |
E815973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liberal Protestant movement |
C14901
|
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: liberal Protestant movement Context triple: [Boston Unitarianism, instanceOf, liberal Protestant movement]
-
A.
Unitarian movement
chosen
The Unitarian movement is a liberal religious tradition that emphasizes the oneness of God, the use of reason in faith, and the inherent worth and dignity of every person, often rejecting traditional doctrines like the Trinity.
-
B.
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.
-
C.
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.
-
D.
Protestant theological movement
A Protestant theological movement is a distinct stream within Protestant Christianity characterized by shared doctrinal emphases, interpretive approaches to Scripture, and practical expressions of faith that differentiate it from other Protestant traditions.
-
E.
humanist religious movement
A humanist religious movement is a faith-oriented community or tradition that centers human dignity, reason, and ethical responsibility while often reinterpreting or minimizing supernatural beliefs.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:08 a.m.