Triple
T2436462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV Journaling Bible |
E52972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Study Bible edition |
C2180
|
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: Study Bible edition Context triple: [ESV Journaling Bible, instanceOf, Study Bible edition]
-
A.
English Bible version
chosen
An English Bible version is a specific translation of the biblical texts into the English language, reflecting particular linguistic choices, theological perspectives, and translation philosophies.
-
B.
Bible translation
A Bible translation is a version of the biblical texts rendered from their original languages into another language, aiming to convey their meaning, style, and theological nuances for a specific audience.
-
C.
critical edition of the Hebrew Bible
A critical edition of the Hebrew Bible is a scholarly reconstruction of the biblical text that compares and evaluates all major manuscripts and textual witnesses to present the most reliable form of the original writings, accompanied by an apparatus documenting significant variants.
-
D.
biblical text
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.
-
E.
critical edition of the Greek New Testament
A critical edition of the Greek New Testament is a scholarly reconstruction of the text based on systematic comparison and evaluation of all available manuscript evidence, accompanied by an apparatus documenting significant textual variants.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:43 p.m.