Triple
T29211041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civaka Cintamani Kaviyam |
E740546
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical Tamil literary work |
C45403
|
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 literary work Context triple: [Civaka Cintamani Kaviyam, instanceOf, classical Tamil literary work]
-
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.
ancient literary work
An ancient literary work is a written composition created in antiquity that reflects the language, culture, beliefs, and artistic expression of early civilizations.
-
C.
Tamil philosophical work
chosen
A Tamil philosophical work is a text composed in the Tamil language that explores fundamental questions about existence, knowledge, ethics, and reality, often integrating indigenous Tamil thought with broader Indian philosophical traditions.
-
D.
place in Tamil literature
A "place in Tamil literature" is a geographically or imaginatively defined location—real, mythical, or symbolic—depicted in Tamil texts that shapes narrative events, cultural context, and thematic meaning.
-
E.
Telugu literary work
A Telugu literary work is a written creation composed in the Telugu language, encompassing genres such as poetry, prose, drama, and criticism that reflect the culture, history, and aesthetics of Telugu-speaking communities.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:11 p.m.