Triple
T23704471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberian codices |
E585680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Masoretic Bible manuscripts |
C47966
|
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: Masoretic Bible manuscripts Context triple: [Tiberian codices, instanceOf, Masoretic Bible manuscripts]
-
A.
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.
-
B.
Tosefta manuscript
A Tosefta manuscript is a handwritten document preserving the text of the Tosefta, an early rabbinic compilation of legal traditions that supplements and parallels the Mishnah.
-
C.
Dead Sea Scroll
A Dead Sea Scroll is an ancient Jewish manuscript, dating from the third century BCE to the first century CE, discovered near the Dead Sea and containing biblical texts, sectarian writings, and other religious documents that illuminate Second Temple Judaism and the origins of early Christianity.
-
D.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
E.
critical edition of the Hebrew Bible
A critical edition of the Hebrew Bible is a scholarly reconstruction of the biblical text that compares and evaluates all major manuscripts and textual witnesses to present the most reliable form of the original writings, accompanied by an apparatus documenting significant variants.
- F. None of above. chosen
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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:53 p.m.