Triple
T19162177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayn Sof |
E469082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish mystical term |
C35186
|
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: Jewish mystical term Context triple: [Ayn Sof, instanceOf, Jewish mystical term]
-
A.
ancient Hebrew concept
chosen
An ancient Hebrew concept is a foundational idea, belief, or category from early Hebrew thought and culture that shaped their understanding of God, the world, and human life.
-
B.
Jewish mystical community
A Jewish mystical community is a group of individuals who gather to study, practice, and embody Jewish esoteric traditions—such as Kabbalah and Hasidic spirituality—through shared rituals, texts, and contemplative practices.
-
C.
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).
-
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.
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.
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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.