Triple
T28681658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torah uMadda |
E726023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish religious philosophy |
C3148
|
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: Jewish religious philosophy Context triple: [Torah uMadda, instanceOf, Jewish religious philosophy]
-
A.
work of Jewish philosophy
A work of Jewish philosophy is a text that systematically explores theological, ethical, metaphysical, or epistemological questions from within Jewish intellectual, scriptural, and cultural traditions.
-
B.
Jewish theological doctrine
Jewish theological doctrine is the body of religious beliefs and interpretations within Judaism concerning God, creation, covenant, law, and the relationship between the divine and the Jewish people.
-
C.
work of Jewish spiritual thought
A work of Jewish spiritual thought is a text or creation that explores, interprets, and deepens Jewish understandings of God, the soul, ethics, and religious life, often drawing on Torah, rabbinic literature, mysticism, and lived experience.
-
D.
branch of Jewish thought
chosen
A branch of Jewish thought is a distinct stream of intellectual, spiritual, or philosophical reflection within Judaism that develops particular interpretations of Jewish texts, beliefs, and practices.
-
E.
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.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 5:09 a.m.