Triple
T28679340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Doctrine of Inerrancy |
E725964
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | work on biblical authority |
C26783
|
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: work on biblical authority Context triple: [The Doctrine of Inerrancy, instanceOf, work on biblical authority]
-
A.
Biblical discourse
Biblical discourse is the structured communication—spoken, written, or interpretive—that engages with, explains, or applies the texts, themes, and theology of the Bible within specific historical, cultural, and religious contexts.
-
B.
New Testament theology work
A New Testament theology work systematically explores the theological themes, teachings, and narrative development of the New Testament writings in their historical and canonical contexts.
-
C.
work of biblical criticism
chosen
A work of biblical criticism is a scholarly text that analyzes the Bible’s origins, composition, historical context, literary features, and theological claims using critical methods and academic tools.
-
D.
biblical theology
Biblical theology is the disciplined study of the progressive revelation, themes, and theology of the Bible as they unfold within their historical and literary contexts across the canon.
-
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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 5:08 a.m.