Triple
T8549386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natrinai |
E202407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical Tamil literature text |
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 literature text Context triple: [Natrinai, instanceOf, classical Tamil literature text]
-
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.
ancient literature
Ancient literature encompasses the written works, myths, epics, religious texts, and philosophical writings produced by early civilizations that reveal their cultures, beliefs, and historical experiences.
-
D.
classical Arabic text
A classical Arabic text is a written work composed in the formal, literary variety of Arabic used from the early Islamic period through the medieval era, characterized by rich rhetoric, precise grammar, and adherence to traditional stylistic norms.
-
E.
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.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:19 p.m.