Triple
T32967640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanhuma midrashim |
E843418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | midrashic work |
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: midrashic work Context triple: [Tanhuma midrashim, instanceOf, midrashic work]
-
A.
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.
-
B.
Mussar literature
Mussar literature is a body of Jewish ethical and spiritual writings focused on character refinement, moral conduct, and the disciplined cultivation of virtuous traits.
-
C.
Jewish apocalyptic work
A Jewish apocalyptic work is a religious text, typically from the Second Temple period, that reveals divine mysteries about the end of days, cosmic conflict, and ultimate judgment through symbolic visions and angelic mediators.
-
D.
Hebrew literary work
A Hebrew literary work is a written creation composed primarily in the Hebrew language, encompassing genres such as poetry, prose, drama, and religious or secular texts that reflect Hebrew culture, history, and thought.
-
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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:21 a.m.