Triple
T18512332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nonconformist Protestants |
E452372
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant group |
C30768
|
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: Protestant group Context triple: [Nonconformist Protestants, instanceOf, Protestant group]
-
A.
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.
-
B.
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.
-
C.
Protestant dissenters
chosen
Protestant dissenters are individuals or groups within Protestantism who separate from or oppose established state or majority churches over matters of doctrine, worship, governance, or conscience.
-
D.
Protestant federation
A Protestant federation is an organized alliance of Protestant churches or denominations that collaborate to coordinate religious activities, represent shared interests, and promote common theological or social goals while maintaining their individual autonomy.
-
E.
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.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:36 a.m.