Triple

T24983696
Position Surface form Disambiguated ID Type / Status
Subject Anavopaya E625242 entity
Predicate instanceOf P0 FINISHED
Object practice in Kashmir Shaivism C18044 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: practice in Kashmir Shaivism
Context triple: [Anavopaya, instanceOf, practice in Kashmir Shaivism]
  • A. Shaivite ascetic tradition
    The Shaivite ascetic tradition is a spiritual path within Hinduism centered on devotion to Shiva, emphasizing renunciation, rigorous yogic and meditative disciplines, and the pursuit of liberation through detachment from worldly life.
  • B. Shaivite tradition
    The Shaivite tradition is a major Hindu devotional and philosophical stream centered on the worship of Shiva as the supreme reality, encompassing diverse rituals, yogic practices, temple cultures, and theological schools across South Asia.
  • C. Tantric tradition chosen
    The Tantric tradition is a diverse set of esoteric spiritual practices and philosophies, originating in South Asia, that use ritual, meditation, visualization, and sometimes transgressive methods to transform ordinary experience into a path to enlightenment and divine union.
  • D. esoteric practice
    An esoteric practice is a specialized, often secret or obscure set of spiritual, mystical, or philosophical techniques intended for a limited group of initiates rather than the general public.
  • E. 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.
  • 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_69e2ff254570819093d197b1900305ac completed April 18, 2026, 3:48 a.m.
Created at: April 18, 2026, 6:02 a.m.