Triple
T20679967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asmodeus |
E508265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | figure in Jewish demonology |
C5130
|
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: figure in Jewish demonology Context triple: [Asmodeus, instanceOf, figure in Jewish demonology]
-
A.
figure in Jewish tradition
chosen
A figure in Jewish tradition is an individual—historical, legendary, or symbolic—who plays a significant role in Jewish religious texts, narratives, law, or cultural memory.
-
B.
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).
-
C.
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).
-
D.
era in Jewish history
An era in Jewish history is a distinct period marked by characteristic religious, cultural, political, and social developments that shape the trajectory and identity of the Jewish people.
-
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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:44 a.m.