Triple

T23629526
Position Surface form Disambiguated ID Type / Status
Subject Testament of Solomon E583568 entity
Predicate instanceOf P0 FINISHED
Object ancient Jewish magical text C36514 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: ancient Jewish magical text
Context triple: [Testament of Solomon, instanceOf, ancient Jewish magical text]
  • A. 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).
  • B. 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.
  • C. Jewish apocalyptic work chosen
    A Jewish apocalyptic work is a religious text, typically from the Second Temple period, that reveals divine mysteries about the end of days, cosmic conflict, and ultimate judgment through symbolic visions and angelic mediators.
  • D. Mandaean religious text
    A Mandaean religious text is a sacred writing of the Mandaean faith that preserves its cosmology, rituals, theology, and ethical teachings in the Mandaic language.
  • E. Manichaean religious text
    A Manichaean religious text is a written work that conveys the dualistic doctrines, cosmology, ethics, and ritual practices of the Manichaean faith, often framed as revelations or teachings from Mani and other divine figures.
  • 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_69e248fc8d74819091bd5baef2f36f6f completed April 17, 2026, 2:51 p.m.
Created at: April 17, 2026, 6:46 p.m.