Triple
T18737648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savitrī |
E458206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Mahābhārata |
C40739
|
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: character in the Mahābhārata Context triple: [Savitrī, instanceOf, character in the Mahābhārata]
-
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.
MahabharataCharacter
chosen
A MahabharataCharacter represents an individual entity from the Indian epic Mahabharata, encapsulating their identity, lineage, allegiances, roles in key events, relationships, and associated attributes such as virtues, flaws, and divine connections.
-
C.
character group in the Mahabharata
A character group in the Mahabharata is a set of individuals—such as families, factions, or allied kingdoms—linked by kinship, loyalty, or shared purpose, whose collective actions and relationships drive the epic’s narrative and moral conflicts.
-
D.
Sangam literature character
A Sangam literature character is an individual, often archetypal, depicted in ancient Tamil Sangam poetry whose actions, emotions, and relationships embody the cultural, ethical, and poetic ideals of early historic South India.
-
E.
character in Silappatikaram
A character in Silappatikaram is an individual—mortal, divine, or symbolic—whose actions, relationships, and moral choices drive the epic’s exploration of justice, fate, and dharma in ancient Tamil society.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:51 a.m.