Triple
T2397960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judah ha-Nasi |
E47694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | compiler of the Mishnah |
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: compiler of the Mishnah Context triple: [Judah ha-Nasi, instanceOf, compiler of the Mishnah]
-
A.
compilation of oral law
A compilation of oral law is an organized written collection of previously unwritten legal traditions, interpretations, and rulings that were transmitted orally within a community or religious-legal system.
-
B.
critical edition of the Hebrew Bible
A critical edition of the Hebrew Bible is a scholarly reconstruction of the biblical text that compares and evaluates all major manuscripts and textual witnesses to present the most reliable form of the original writings, accompanied by an apparatus documenting significant variants.
-
C.
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.
-
D.
Jewish interpretive technique
A Jewish interpretive technique is a systematic method used to analyze, explain, and derive meaning from Jewish texts—especially the Hebrew Bible and rabbinic literature—through established hermeneutic principles and traditions.
-
E.
Byzantine jurist
A Byzantine jurist is a legal scholar or judge of the Byzantine Empire who interpreted, applied, and commented on Roman and Byzantine law within the empire’s complex religious and imperial framework.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:57 p.m.