Triple
T4768790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shevirat ha-Kelim |
E105874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lurianic Kabbalistic doctrine |
C17361
|
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: Lurianic Kabbalistic doctrine Context triple: [Shevirat ha-Kelim, instanceOf, Lurianic Kabbalistic doctrine]
-
A.
Kabbalist
A Kabbalist is a practitioner and scholar of Jewish mystical tradition who studies and applies esoteric teachings about the nature of the divine, the universe, and the human soul.
-
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.
Renaissance esotericism
Renaissance esotericism is the complex of mystical, occult, and hermetic philosophies and practices that flourished in early modern Europe, blending classical, Christian, and magical traditions in the pursuit of hidden spiritual and cosmic knowledge.
-
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 numerological system
A Jewish numerological system is a symbolic framework, such as gematria, that assigns numerical values to Hebrew letters and words to uncover hidden meanings, spiritual insights, and interpretive connections within Jewish texts and traditions.
- F. None of above. chosen
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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:21 p.m.