Triple
T9310692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbinic literature |
E223998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish text corpus |
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: Jewish text corpus Context triple: [Rabbinic literature, instanceOf, Jewish text corpus]
-
A.
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.
-
B.
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.
-
C.
Jewish biblical edition
A Jewish biblical edition is a published version of the Hebrew Bible (Tanakh) that reflects Jewish textual traditions, often including the Masoretic text, traditional cantillation marks, commentaries, and sometimes translations aligned with Jewish interpretation.
-
D.
Jewish studies library
A Jewish studies library is a specialized collection of books, manuscripts, and digital resources focused on Jewish history, religion, culture, languages, and thought, curated to support research, education, and community learning.
-
E.
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.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.