Triple
T32940101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bible—Translations into English |
E842643
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical translation corpus |
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: biblical translation corpus Context triple: [Bible—Translations into English, instanceOf, biblical translation corpus]
-
A.
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.
-
B.
polyglot Bible
A polyglot Bible is an edition of the Scriptures that presents the biblical text in multiple languages side by side to facilitate comparison, study, and translation.
-
C.
biblical text edition
A biblical text edition is a curated version of the Bible that presents a specific text form, often with scholarly annotations, critical apparatus, translations, and editorial decisions to support study, interpretation, or liturgical use.
-
D.
sources for New Testament textual criticism
Sources for New Testament textual criticism are the manuscripts, early translations, and patristic citations that provide the textual evidence used to reconstruct and evaluate the original wording of the New Testament writings.
-
E.
Bible translation committee
A Bible translation committee is a group of scholars, linguists, and theologians who collaboratively translate biblical texts from their original languages into a target language, ensuring accuracy, clarity, and faithfulness to the source.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.