Triple
T31731300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Brethren |
E809865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anabaptist Christian group |
C3627
|
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: Anabaptist Christian group Context triple: [River Brethren, instanceOf, Anabaptist Christian group]
-
A.
Christian heterodox group
A Christian heterodox group is a community or movement that identifies as Christian but holds beliefs or practices that significantly diverge from established orthodox Christian doctrine.
-
B.
Christian restorationist movement
chosen
A Christian restorationist movement is a religious reform effort that seeks to return Christianity to what it understands as the beliefs, practices, and organizational patterns of the early New Testament church, often rejecting later traditions and creeds.
-
C.
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.
-
D.
Mennonite organization
A Mennonite organization is a faith-based group rooted in Anabaptist-Mennonite beliefs that coordinates religious, educational, service, or relief activities in alignment with Mennonite theology and community values.
-
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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:21 p.m.