Triple
T5727092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safed Kabbalah |
E126291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | school of Jewish mysticism |
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: school of Jewish mysticism Context triple: [Safed Kabbalah, instanceOf, school of Jewish mysticism]
-
A.
Lurianic Kabbalistic doctrine
A mystical Jewish theological framework developed by Rabbi Isaac Luria that explains creation, divine contraction (tzimtzum), cosmic shattering (shevirat ha-kelim), and the human role in restoring harmony to the universe through spiritual repair (tikkun).
-
B.
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.
-
C.
Christian Kabbalistic work
A Christian Kabbalistic work is a text that interprets Jewish Kabbalistic concepts through a Christian theological lens, often aiming to reveal or support Christian doctrines using mystical Jewish symbolism and methods.
-
D.
Christian Kabbalistic reinterpretation
Christian Kabbalistic reinterpretation is the adaptation of Jewish Kabbalistic concepts, symbols, and texts into a Christian theological framework, often to support doctrines such as the Trinity, Christology, and salvation history.
-
E.
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.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:47 p.m.