Triple
T9714465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humash |
E235105
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish scripture |
C609
|
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 scripture Context triple: [Humash, instanceOf, Jewish scripture]
-
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 literature
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 religious document
A Jewish religious document is a written text that conveys, preserves, or interprets Jewish beliefs, laws, rituals, history, or ethical teachings within the Jewish tradition.
-
D.
religious scripture
chosen
A religious scripture is a revered written text or collection of texts that a faith community regards as divinely inspired or authoritative in matters of belief, morality, and spiritual practice.
-
E.
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.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:19 p.m.