Triple
T4882291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paippalada |
E109357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vedic textual tradition |
C1770
|
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: Vedic textual tradition Context triple: [Paippalada, instanceOf, Vedic textual tradition]
-
A.
Sanskrit literature
chosen
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.
-
B.
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.
-
C.
Veda
Veda is a conceptual class representing a comprehensive body of sacred or foundational knowledge that serves as an authoritative source for understanding and guiding a particular domain or system.
-
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.
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.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:27 p.m.