Triple
T917723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaddai |
E19806
|
entity |
| Predicate | mentionedIn |
P831
|
FINISHED |
| Object | Midrash |
E44494
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Midrash | Statement: [Shaddai, mentionedIn, Midrash]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Midrash Context triple: [Shaddai, mentionedIn, Midrash]
-
A.
Midrash
chosen
Midrash is a classical Jewish literary and interpretive tradition that explores, explains, and expands upon the Hebrew Bible through narrative, legal, and ethical teachings.
-
B.
Midrash halakha
Midrash halakha is a genre of rabbinic literature that derives and interprets Jewish legal rulings from the biblical text.
-
C.
Aggadah
Aggadah is the non-legal component of rabbinic literature, encompassing narrative, ethical teachings, theology, and folklore found in the Talmud and Midrash.
-
D.
Talmud
The Talmud is a central Jewish religious text comprising rabbinic discussions, legal rulings, and interpretations of the Hebrew Bible that form the foundation of traditional Jewish law and theology.
-
E.
Targums
Targums are ancient Aramaic translations and paraphrases of the Hebrew Bible that were used in Jewish worship and study.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2fa7b0081909155afc12c1ab630 |
completed | March 1, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac16fbe454819085020fc245c959ed |
completed | March 7, 2026, 12:15 p.m. |
Created at: March 1, 2026, 7:40 p.m.