Triple
T5524795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Marrow of Theology |
E144896
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Reformed theology work |
C12260
|
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: Reformed theology work Context triple: [The Marrow of Theology, instanceOf, Reformed theology work]
-
A.
Reformed theology text
chosen
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.
theological work
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.
-
C.
Reformation-era theologian
A Reformation-era theologian is a religious scholar from the 16th-century Protestant or Catholic reform movements who developed, debated, and systematized doctrines that reshaped Western Christianity.
-
D.
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.
-
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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:34 p.m.