Triple

T10476615
Position Surface form Disambiguated ID Type / Status
Subject Adipurana E247059 entity
Predicate instanceOf P0 FINISHED
Object Jain religious text C16429 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: Jain religious text
Context triple: [Adipurana, instanceOf, Jain religious text]
  • A. Hindu religious texts
    Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
  • B. Vedantic treatise
    A Vedantic treatise is a systematic philosophical work that explicates, analyzes, and interprets the core metaphysical, epistemological, and spiritual doctrines of Vedanta, often through commentary on foundational scriptures like the Upanishads, Bhagavad Gita, and Brahma Sutras.
  • C. Sutra literature chosen
    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.
  • D. Taoist text
    A Taoist text is a written work that conveys the philosophies, practices, and cosmological views of Taoism, often emphasizing harmony with the Tao, naturalness, and effortless action.
  • E. Samkhya text
    A Samkhya text is a philosophical work rooted in the ancient Indian Samkhya system that systematically analyzes reality through the dual principles of purusha (consciousness) and prakriti (primordial matter) to explain cosmology, psychology, and liberation.
  • 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_69d381c16c248190a2fe5b471e584e9c completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 12:21 p.m.