Triple
T10123111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Standard Version |
E223346
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bible version |
C1832
|
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: Bible version Context triple: [American Standard Version, instanceOf, Bible version]
-
A.
English Bible version
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
chosen
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.
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.
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.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:05 p.m.