Triple
T22132245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heavenly ascents |
E546932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | motif in Jewish mystical literature |
C12785
|
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: motif in Jewish mystical literature Context triple: [heavenly ascents, instanceOf, motif in Jewish mystical literature]
-
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.
cultural motif
chosen
A cultural motif is a recurring symbolic element, theme, or pattern within a culture’s art, stories, rituals, or practices that conveys shared meanings and values.
-
C.
Mussar literature
Mussar literature is a body of Jewish ethical and spiritual writings focused on character refinement, moral conduct, and the disciplined cultivation of virtuous traits.
-
D.
Jewish mystical text edition
A Jewish mystical text edition is a curated, scholarly presentation of one or more kabbalistic or other esoteric Jewish works, typically including a critical text, annotations, translations, and contextual commentary.
-
E.
Lurianic Kabbalah text
A Lurianic Kabbalah text is a work that presents, explains, or elaborates on the mystical doctrines of Rabbi Isaac Luria, focusing on concepts such as tzimtzum (divine contraction), shevirat ha-kelim (shattering of the vessels), and tikkun (cosmic repair).
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:32 p.m.