Triple
T12745389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talmud Yerushalmi |
E304590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical Jewish 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: classical Jewish work Context triple: [Talmud Yerushalmi, instanceOf, classical Jewish work]
-
A.
Jewish historical work
A Jewish historical work is a text that records, interprets, and reflects on the experiences, events, and developments of Jewish people and communities across time, often integrating religious, cultural, and social perspectives.
-
B.
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.
-
C.
work of Jewish philosophy
A work of Jewish philosophy is a text that systematically explores theological, ethical, metaphysical, or epistemological questions from within Jewish intellectual, scriptural, and cultural traditions.
-
D.
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.
-
E.
Judeo-Arabic work
A Judeo-Arabic work is a text written in Arabic using Hebrew script, typically produced by Jewish communities in the medieval Islamic world for religious, philosophical, or everyday purposes.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.