Triple
T19594757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riksharaja |
E470322
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Ramayana tradition |
C18232
|
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 Ramayana tradition Context triple: [Riksharaja, instanceOf, character in the Ramayana tradition]
-
A.
Character in the Ramayana
chosen
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.
figure in Hindu tradition
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.
-
C.
event in the Ramayana
An event in the Ramayana is a significant occurrence or episode—such as a battle, journey, divine intervention, or moral turning point—that advances the epic’s narrative and reveals the characters’ virtues, flaws, and dharma.
-
D.
kanda of the Ramayana
The kanda of the Ramayana is a major book or section of the epic, each focusing on a distinct phase of Lord Rama’s life and the unfolding of the narrative.
-
E.
episode in Hindu mythology
An episode in Hindu mythology is a distinct narrative unit—such as a story, incident, or event—within the larger mythic tradition that illustrates moral, philosophical, or cosmological themes through the actions of divine, heroic, or supernatural figures.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.