Triple
T1237909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patripassianism |
E26589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Christian heresy |
C1835
|
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: early Christian heresy Context triple: [Patripassianism, instanceOf, early Christian heresy]
-
A.
Christian heresy
chosen
A Christian heresy is a belief or teaching that claims to be Christian yet significantly deviates from the established doctrines defined as orthodox by the historic Christian Church.
-
B.
early Christian church
The early Christian church was the loosely organized community of Jesus’ followers in the first few centuries CE, developing its beliefs, practices, and leadership structures as it spread throughout the Roman Empire and beyond.
-
C.
heresy in mainstream Christianity
Heresy in mainstream Christianity is a belief, teaching, or practice that significantly deviates from established orthodox doctrine and is formally rejected by the church’s recognized authorities.
-
D.
2nd-century Christian
A 2nd-century Christian is a follower of Jesus within the diverse and developing early Church of the 100s CE, navigating emerging doctrines, sporadic persecution, and the transition from apostolic tradition to organized theology and community life.
-
E.
Roman imperial persecution
Roman imperial persecution refers to the episodic, state-sanctioned suppression, punishment, and coercion of religious or political groups—most notably Christians—by Roman authorities, driven by concerns over public order, imperial unity, and traditional religious norms.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.