Triple
T25255955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhra Mahabharatam |
E633173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu epic literature |
C22098
|
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: Hindu epic literature Context triple: [Andhra Mahabharatam, instanceOf, Hindu epic literature]
-
A.
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.
-
B.
Hindu religious texts
chosen
Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
-
C.
entity in Indian epic tradition
An entity in the Indian epic tradition is any person, creature, deity, or supernatural being that participates in the narrative, cosmology, or moral framework of epics like the Mahābhārata and Rāmāyaṇa.
-
D.
book of the Mahābhārata
A book of the Mahābhārata is a major division of the epic that organizes its narrative, teachings, and episodes into a distinct, thematically coherent section of the larger work.
-
E.
Indian literature
Indian literature encompasses the diverse body of written and oral works produced in the many languages of the Indian subcontinent, reflecting its rich cultural, religious, and historical traditions from ancient times to the present.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:13 p.m.