Triple
T21847730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meykanda Shastras |
E539419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tamil religious literature |
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 religious literature Context triple: [Meykanda Shastras, instanceOf, Tamil religious 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.
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.
-
D.
Sikh religious literature
Sikh religious literature encompasses the sacred scriptures, hymns, commentaries, and historical writings that articulate Sikh theology, ethics, devotional practice, and community identity, centered on the Guru Granth Sahib and related texts.
-
E.
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.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:55 p.m.