Triple
T19869406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shilpa Shastras |
E477472
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu technical scripture |
C42441
|
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: Hindu technical scripture Context triple: [Shilpa Shastras, instanceOf, Hindu technical scripture]
-
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.
Hindu reformist text
A Hindu reformist text is a written work that critiques existing religious practices and beliefs within Hinduism and advocates changes to align them with contemporary ethical, social, or rational ideals.
-
D.
Shaivite scripture
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.
-
E.
Hindu astronomical work
A Hindu astronomical work is a traditional Indian text that systematically describes celestial bodies, their motions, and related mathematical and calendrical calculations within the framework of Hindu cosmology.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.