Triple
T3718177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emunot ve-Deot |
E81579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Jewish text |
C3961
|
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: medieval Jewish text Context triple: [Emunot ve-Deot, instanceOf, medieval Jewish text]
-
A.
rabbinic text
chosen
A rabbinic text is a work produced by Jewish sages that records their interpretations, legal rulings, narratives, and theological reflections on the Hebrew Bible and Jewish law.
-
B.
medieval prose text
A medieval prose text is a written work from the Middle Ages composed in continuous, non-verse form, often preserving narratives, religious teachings, legal codes, or historical accounts in the vernacular or Latin.
-
C.
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.
-
D.
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.
-
E.
medieval Jewish philosopher
A medieval Jewish philosopher is a thinker from roughly the 9th to 15th centuries who engaged with Jewish religious tradition and texts using the philosophical methods and ideas of their time, often integrating Jewish theology with Greco-Arabic and scholastic thought.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.