Triple
T34414190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Doctrine of the Word of God |
E883357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | volume of systematic theology |
C40626
|
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: volume of systematic theology Context triple: [The Doctrine of the Word of God, instanceOf, volume of systematic theology]
-
A.
Lutheran systematic theology
Lutheran systematic theology is the ordered, doctrinal articulation of Christian faith from a Lutheran perspective, integrating Scripture, the Lutheran Confessions, and theological tradition into a coherent framework for belief and practice.
-
B.
doctrinal system
A doctrinal system is an organized, coherent set of principles, beliefs, or teachings that provides a structured framework for understanding, interpreting, and guiding thought or behavior within a particular domain.
-
C.
theological series
chosen
A theological series is a structured sequence of works—such as lectures, books, sermons, or videos—that systematically explores religious doctrines, beliefs, and practices around a unifying theological theme.
-
D.
theological journal
A theological journal is a periodical publication that presents scholarly research, critical essays, and reflections on religious beliefs, doctrines, practices, and their implications for faith and society.
-
E.
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.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.