Triple

T5248081
Position Surface form Disambiguated ID Type / Status
Subject Tirumurai E118512 entity
Predicate instanceOf P0 FINISHED
Object Shaivite scripture C18236 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: Shaivite scripture
Context triple: [Tirumurai, instanceOf, Shaivite scripture]
  • A. Shaiva scripture commentary
    A Shaiva scripture commentary is an interpretive text that explains, analyzes, and contextualizes sacred Shaiva scriptures, clarifying their philosophical, ritual, and devotional meanings for practitioners and scholars.
  • B. Sutra literature
    Sutra literature is a body of sacred texts, primarily in Hinduism, Buddhism, and Jainism, composed in concise aphoristic form to systematically present spiritual teachings, doctrines, and practices.
  • C. Mahavidya
    Mahavidya is a conceptual class representing each of the ten great wisdom goddesses in Hindu Tantric tradition, embodying distinct cosmic powers, philosophical insights, and transformative spiritual functions.
  • D. Gaudiya Vaishnava scripture commentary
    A Gaudiya Vaishnava scripture commentary is an exegetical work that explains, interprets, and contextualizes sacred texts—such as the Bhagavad-gītā, Śrīmad-Bhāgavatam, and Chaitanya-caritāmṛta—according to the theological, devotional, and philosophical perspectives of the Gaudiya Vaishnava tradition.
  • E. 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).
  • F. None of above. chosen

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_69bd4468aacc8190a8196f71855cdf4f completed March 20, 2026, 12:58 p.m.
Created at: March 20, 2026, 1:50 p.m.