Triple
T20321116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | commentaries of Maimonides |
E492208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rabbinic commentary 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: rabbinic commentary corpus Context triple: [commentaries of Maimonides, instanceOf, rabbinic commentary corpus]
-
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.
Jewish biblical commentary
Jewish biblical commentary is a tradition of interpretive writings that explain, analyze, and expand upon the Hebrew Bible’s text, language, and meaning from religious, legal, ethical, and historical perspectives.
-
D.
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.
-
E.
commentary on Shulchan Aruch
A commentary on the Shulchan Aruch is a scholarly work that explains, analyzes, and clarifies the legal rulings of this foundational Jewish code of law, often reconciling sources and applying them to practical halachic questions.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:20 a.m.