Triple
T3976699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikraot Gedolot |
E85660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rabbinic Bible |
C2501
|
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: rabbinic Bible Context triple: [Mikraot Gedolot, instanceOf, rabbinic Bible]
-
A.
rabbinic text
A rabbinic text is a work produced by Jewish sages that records their interpretations, legal rulings, narratives, and theological reflections on the Hebrew Bible and Jewish law.
-
B.
rabbinic literature
chosen
Rabbinic literature is the body of Jewish religious writings produced by rabbinic sages, including the Mishnah, Talmud, Midrash, and related commentaries, that interpret and expand upon the Hebrew Bible and Jewish law.
-
C.
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.
-
D.
Ketuvim book
A Ketuvim book is a work within the third section of the Hebrew Bible, comprising diverse writings such as poetry, wisdom literature, and historical narratives.
-
E.
Jewish interpretive technique
A Jewish interpretive technique is a systematic method used to analyze, explain, and derive meaning from Jewish texts—especially the Hebrew Bible and rabbinic literature—through established hermeneutic principles and 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:33 p.m.