Triple
T8564508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tolkāppiyam |
E202770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical Tamil work |
C9096
|
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: classical Tamil work Context triple: [Tolkāppiyam, instanceOf, classical Tamil work]
-
A.
classical Tamil literature
chosen
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.
classical language
A classical language is an ancient, historically significant language with a rich literary tradition that continues to influence later cultures, languages, and scholarship.
-
D.
classical language of India
A classical language of India is an ancient, historically significant Indian language with a rich literary tradition and documented history over a long period, recognized for its cultural and scholarly importance.
-
E.
variety of Tamil
A variety of Tamil is a distinct form of the Tamil language characterized by unique phonological, lexical, and grammatical features associated with a particular region, social group, or communicative context.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:20 p.m.