Triple
T19074615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Westminster Company for the King James Bible |
E466872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | King James Bible translation company |
C5615
|
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: King James Bible translation company Context triple: [First Westminster Company for the King James Bible, instanceOf, King James Bible translation company]
-
A.
Bible translation committee
chosen
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.
-
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.
Bible society
A Bible society is an organization dedicated to translating, publishing, and distributing the Bible, often aiming to make it accessible and affordable to people worldwide.
-
D.
Gutenberg Bible
The Gutenberg Bible is the first major book printed in Europe using movable metal type by Johannes Gutenberg in the mid-15th century, marking the start of the age of mass-produced printed books.
-
E.
Unitarian edition of the New Testament
A Unitarian edition of the New Testament is a version of the Christian scriptures edited and annotated from a Unitarian theological perspective, emphasizing the unity of God and rejecting traditional Trinitarian doctrine.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.