Triple
T5450976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loci Communes |
E122368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant 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: Protestant theological work Context triple: [Loci Communes, instanceOf, Protestant 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.
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.
-
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.
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.
-
E.
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.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.