Triple
T8549921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhavi |
E202419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sangam literature character |
C24613
|
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: Sangam literature character Context triple: [Madhavi, instanceOf, Sangam literature character]
-
A.
Character in the Ramayana
A Character in the Ramayana is an individual—divine, human, or demonic—whose actions, relationships, and moral choices drive the epic’s narrative and embody its spiritual and ethical teachings.
-
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.
medieval Telugu poet
A medieval Telugu poet is a literary figure from roughly the 11th to 17th centuries who composed poetry in the Telugu language, often blending devotional, courtly, and philosophical themes within the cultural and political milieu of South India.
-
D.
Sanskrit writer
A Sanskrit writer is an individual who composes, translates, or interprets texts in the Sanskrit language, contributing to its literary, philosophical, or scholarly traditions.
-
E.
character in Shahnameh
A character in Shahnameh is a mytho-historical figure—heroic, royal, or demonic—whose actions, lineage, and moral choices drive the epic’s intertwined tales of Iran’s legendary past.
- F. None of above. chosen
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.