Triple
T19082060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronistic History |
E467056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical corpus |
C623
|
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: biblical corpus Context triple: [Chronistic History, instanceOf, biblical corpus]
-
A.
biblical text
chosen
A biblical text is a written work that forms part of the Bible, conveying religious narratives, laws, teachings, and poetry considered sacred and authoritative within Jewish and Christian traditions.
-
B.
bibliographical corpus
A bibliographical corpus is a structured collection of bibliographic records or references, typically compiled for systematic analysis, cataloging, or research on published works.
-
C.
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.
-
D.
biblical studies resource
A biblical studies resource is a tool, text, or digital aid designed to support the scholarly and devotional study, interpretation, and teaching of the Bible and its historical, literary, and theological contexts.
-
E.
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.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.