Triple
T11462209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwinglianism |
E271688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Protestant theology |
C28681
|
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: branch of Protestant theology Context triple: [Zwinglianism, instanceOf, branch of Protestant theology]
-
A.
branch of Christian theology
A branch of Christian theology is a specialized field of study within Christian thought that systematically explores a particular aspect of faith, doctrine, or practice (such as Christology, ecclesiology, or soteriology).
-
B.
branch of Christian studies
A branch of Christian studies is a specialized field of theological inquiry that focuses on a particular aspect of Christian belief, practice, history, or scripture within the broader discipline of Christian theology.
-
C.
branch of Christianity
A branch of Christianity is a distinct tradition within the Christian faith, defined by shared doctrines, practices, and organizational structures that differentiate it from other Christian groups.
-
D.
Protestant theological movement
chosen
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.
Reformed theology text
A Reformed theology text is a written work that systematically presents and explains Christian doctrine from the perspective of the Reformed tradition, emphasizing God’s sovereignty, covenant theology, and the authority of Scripture.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:35 p.m.