Triple
T7292474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Turim |
E164430
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval rabbinic text |
C3961
|
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: medieval rabbinic text Context triple: [The Turim, instanceOf, medieval rabbinic text]
-
A.
rabbinic text
chosen
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
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.
medieval Hebrew lexicographical work
A medieval Hebrew lexicographical work is a scholarly text from the Middle Ages that systematically defines, explains, and often translates Hebrew words, typically for biblical, liturgical, or grammatical study.
-
D.
Lurianic Kabbalah text
A Lurianic Kabbalah text is a work that presents, explains, or elaborates on the mystical doctrines of Rabbi Isaac Luria, focusing on concepts such as tzimtzum (divine contraction), shevirat ha-kelim (shattering of the vessels), and tikkun (cosmic repair).
-
E.
Jewish liturgical corpus
The Jewish liturgical corpus is the body of prayers, blessings, poems, and scriptural readings developed across Jewish history and communities for use in communal and private worship throughout the religious calendar and life-cycle events.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3 p.m.