Triple
T11752355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican realignment |
E279437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican movement |
C17579
|
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: Anglican movement Context triple: [Anglican realignment, instanceOf, Anglican movement]
-
A.
movement within Anglicanism
chosen
A movement within Anglicanism is a distinct stream of thought and practice that seeks to renew, reform, or emphasize particular theological, liturgical, or social aspects of Anglican faith and church life.
-
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.
Unitarian movement
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.
-
D.
independent church movement
An independent church movement is a collective trend of congregations or denominations that operate autonomously from established ecclesiastical hierarchies, often emphasizing local governance, contextual theology, and freedom from traditional denominational control.
-
E.
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.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.