Triple
T20602689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirumandiram |
E506222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tamil Shaiva 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: Tamil Shaiva scripture Context triple: [Tirumandiram, instanceOf, Tamil Shaiva scripture]
-
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.
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.
-
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.
Vaishnava scriptures
Vaishnava scriptures are sacred Hindu texts that focus on the worship, teachings, and stories of Vishnu and his avatars, guiding devotees in theology, devotion, and practice.
-
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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.