Triple

T13451349
Position Surface form Disambiguated ID Type / Status
Subject Sefer HaMavet E320613 entity
Predicate instanceOf P0 FINISHED
Object Jewish liturgical work C16573 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 liturgical work
Context triple: [Sefer HaMavet, instanceOf, Jewish liturgical work]
  • A. Jewish liturgical corpus chosen
    The Jewish liturgical corpus is the body of prayers, blessings, poems, and scriptural readings developed across Jewish history and communities for use in communal and private worship throughout the religious calendar and life-cycle events.
  • B. Hebrew religious work
    A Hebrew religious work is a text composed primarily in Hebrew that expresses, interprets, or transmits Jewish religious beliefs, laws, rituals, ethics, or spiritual teachings.
  • C. Yemenite Jewish liturgical tradition
    The Yemenite Jewish liturgical tradition is a distinctive, meticulously preserved rite of prayer, chant, and scriptural recitation that reflects ancient Near Eastern Jewish practices, precise Hebrew pronunciation, and unique musical and textual customs developed within the Jewish communities of Yemen.
  • D. work of Jewish spiritual thought
    A work of Jewish spiritual thought is a text or creation that explores, interprets, and deepens Jewish understandings of God, the soul, ethics, and religious life, often drawing on Torah, rabbinic literature, mysticism, and lived experience.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
Created at: April 9, 2026, 9:41 p.m.