Triple
T23437484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Śivastotrāvalī |
E563503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Śaiva religious text |
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: Śaiva religious text Context triple: [Śivastotrāvalī, instanceOf, Śaiva religious text]
-
A.
Shaivite scripture
chosen
A Shaivite scripture is a sacred Hindu text that centers on the worship, mythology, philosophy, and rituals associated with the god Shiva and his manifestations.
-
B.
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.
-
C.
Shakta scriptures
Shakta scriptures are sacred Hindu texts that focus on the worship of the Divine Mother (Shakti) as the supreme reality, encompassing philosophical teachings, rituals, hymns, and mythological narratives.
-
D.
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.
-
E.
Hindu technical scripture
A Hindu technical scripture is a specialized sacred text that systematically presents practical knowledge—such as ritual procedures, architecture, arts, sciences, or governance—within a Hindu religious and philosophical framework.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 5:50 p.m.