Triple
T20964751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakshmana Rekha |
E516337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | element of the Ramayana tradition |
C42156
|
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: element of the Ramayana tradition Context triple: [Lakshmana Rekha, instanceOf, element of the Ramayana tradition]
-
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.
event in the Ramayana
chosen
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.
-
C.
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.
-
D.
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.
-
E.
adaptation of the Ramayana
An adaptation of the Ramayana is a creative reinterpretation of the ancient Indian epic’s characters, themes, and narrative—often updated in form, setting, or perspective—while retaining its core storyline of Rama’s journey, exile, and battle against Ravana.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:32 p.m.