Triple
T5248082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirumurai |
E118512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tamil devotional literature |
C17458
|
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 devotional literature Context triple: [Tirumurai, instanceOf, Tamil devotional literature]
-
A.
classical Tamil literature
Classical Tamil literature encompasses the ancient poetic, philosophical, and didactic works composed primarily between 300 BCE and 300 CE in Tamil, including the Sangam corpus and later ethical and devotional texts that shaped South Indian culture and thought.
-
B.
Sanskrit literature
Sanskrit literature is the body of classical and post-classical writings in the Sanskrit language, encompassing religious scriptures, epic poetry, drama, philosophy, science, and aesthetics that shaped much of South Asian intellectual and cultural history.
-
C.
Hindu devotional hymn
chosen
A Hindu devotional hymn is a sacred song or chant expressing love, reverence, and supplication to a deity, often performed in worship, rituals, or personal devotion.
-
D.
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.
-
E.
Sutra literature
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.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:50 p.m.