Triple
T15975080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masoretic Text |
E387422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical manuscript tradition |
C1984
|
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 manuscript tradition Context triple: [Masoretic Text, instanceOf, biblical manuscript tradition]
-
A.
Biblical manuscript tradition
chosen
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
B.
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.
-
C.
ancient manuscripts
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
-
D.
Septuagint manuscript
A Septuagint manuscript is a handwritten copy of the ancient Greek translation of the Hebrew Bible (and related texts), produced and transmitted by scribes in antiquity and the medieval period.
-
E.
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.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.