Triple
T3704567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishonim |
E80860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical period in rabbinic literature |
C13632
|
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: historical period in rabbinic literature Context triple: [Rishonim, instanceOf, historical period in rabbinic literature]
-
A.
rabbinic era
chosen
The rabbinic era is the historical period, roughly from the 1st to the 7th century CE, during which rabbinic Judaism developed its foundational texts, institutions, and legal traditions following the destruction of the Second Temple.
-
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.
rabbinic leadership period
The rabbinic leadership period is a historical era in which rabbis emerged as the central religious, legal, and communal authorities in Jewish life, shaping practice and interpretation after the decline of the Temple-based system.
-
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.
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.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.