Triple
T5558157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefer Shoftim |
E145699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | book of Mishneh Torah |
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: book of Mishneh Torah Context triple: [Sefer Shoftim, instanceOf, book of Mishneh Torah]
-
A.
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.
-
B.
Nasi of the Sanhedrin
The Nasi of the Sanhedrin was the president and highest-ranking official of the ancient Jewish high court, responsible for leading its deliberations, representing the Jewish people to external authorities, and guiding religious and legal policy.
-
C.
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.
-
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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:36 p.m.