Triple
T348494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanakh |
E6991
|
entity |
| Predicate | basisFor |
P125
|
FINISHED |
| Object | Halakha |
E4525
|
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: Halakha | Statement: [Tanakh, basisFor, Halakha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Halakha Context triple: [Tanakh, basisFor, Halakha]
-
A.
Halakha
chosen
Halakha is the comprehensive body of traditional Jewish religious law and practice derived from the Torah, Talmud, and later rabbinic rulings.
-
B.
Midrash halakha
Midrash halakha is a genre of rabbinic literature that derives and interprets Jewish legal rulings from the biblical text.
-
C.
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.
-
D.
Mishneh Torah
Mishneh Torah is a comprehensive 12th-century Jewish legal code by Maimonides that systematically organizes and clarifies all of Jewish law.
-
E.
Shulchan Aruch
Shulchan Aruch is a seminal 16th-century codification of Jewish law that serves as the primary halachic reference for much of the Jewish world.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3d7ecd23881909e10bb84f266d2d1 |
completed | March 1, 2026, 6:08 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.