Triple

T11006976
Position Surface form Disambiguated ID Type / Status
Subject Assumption of Moses E260142 entity
Predicate instanceOf P0 FINISHED
Object Jewish apocryphal work C12106 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 apocryphal work
Context triple: [Assumption of Moses, instanceOf, Jewish apocryphal work]
  • A. apocryphal book chosen
    An apocryphal book is a work of uncertain or disputed authorship or canonical status, often associated with religious traditions but not officially accepted into the standard scriptural canon.
  • B. Old Testament apocrypha
    Old Testament apocrypha are a collection of ancient Jewish writings, not included in the Hebrew Bible, that expand upon or supplement Old Testament narratives and teachings and are considered canonical by some Christian traditions but not by others.
  • C. Jewish historical work
    A Jewish historical work is a text that records, interprets, and reflects on the experiences, events, and developments of Jewish people and communities across time, often integrating religious, cultural, and social perspectives.
  • D. 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).
  • 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_69d6aa8a6a548190a750f944ccdc8064 completed April 8, 2026, 7:20 p.m.
Created at: April 8, 2026, 9:25 p.m.