Triple
T6340358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthodox Study Bible |
E142608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English-language 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: English-language Bible edition Context triple: [Orthodox Study Bible, instanceOf, English-language 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.
Jewish biblical edition
A Jewish biblical edition is a published version of the Hebrew Bible (Tanakh) that reflects Jewish textual traditions, often including the Masoretic text, traditional cantillation marks, commentaries, and sometimes translations aligned with Jewish interpretation.
-
D.
English-language book
An English-language book is a written or printed work consisting of pages bound together that primarily uses the English language to convey its content.
-
E.
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.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:30 p.m.