Triple
T2257671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV MacArthur Study Bible |
E49764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian 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: Christian Bible edition Context triple: [ESV MacArthur Study Bible, instanceOf, Christian 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.
Christian prayer book
A Christian prayer book is a collection of written prayers, liturgies, and devotional texts organized to guide individuals or congregations in worship and personal devotion according to Christian tradition.
-
C.
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.
-
D.
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.
-
E.
Christian text tradition
The Christian text tradition is the historical process by which Christian writings—especially the Bible and related theological, liturgical, and devotional texts—are composed, transmitted, translated, interpreted, and canonized within Christian communities over time.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:48 p.m.