Triple
T11269720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation of Christian Doctrine |
E266779
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anabaptist theological work |
C5743
|
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 theological work Context triple: [Foundation of Christian Doctrine, instanceOf, Anabaptist theological work]
-
A.
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.
-
B.
Christian theological corpus
The Christian theological corpus is the body of writings, doctrines, and interpretive traditions that systematically articulate and reflect on Christian beliefs about God, Christ, salvation, the Church, and the ultimate destiny of creation.
-
C.
Christian polemical work
A Christian polemical work is a text written from a Christian perspective that argues against, critiques, or refutes opposing religious, philosophical, or ideological positions to defend or promote Christian doctrine.
-
D.
theological work
chosen
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
-
E.
Christian apologetic work
A Christian apologetic work is a text or presentation that systematically defends and explains the truth claims of Christianity using theological, philosophical, historical, and sometimes scientific arguments.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.