Triple
T19723047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partzufim |
E473657
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | doctrine in Jewish mysticism |
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: doctrine in Jewish mysticism Context triple: [Partzufim, instanceOf, doctrine in Jewish mysticism]
-
A.
Lurianic Kabbalistic doctrine
chosen
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.
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.
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.
-
D.
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.
-
E.
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.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.