Triple
T18399837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyumatsena |
E449962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the legend of Savitri and Satyavan |
C17759
|
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 legend of Savitri and Satyavan Context triple: [Dyumatsena, instanceOf, character in the legend of Savitri and Satyavan]
-
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.
Hindu legendary couple
A Hindu legendary couple is a pair of figures from Hindu mythology or epic tradition whose relationship embodies idealized virtues such as devotion, dharma, love, and sacrifice, often serving as moral and spiritual exemplars.
-
C.
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.
-
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.
figure in Hindu tradition
chosen
A figure in Hindu tradition is an individual—divine, semi-divine, mythological, or historical—who appears in Hindu scriptures, stories, or practices and embodies particular spiritual, moral, or cultural ideals.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:46 a.m.