Triple

T22376447
Position Surface form Disambiguated ID Type / Status
Subject Vilanka Ramayana E553162 entity
Predicate instanceOf P0 FINISHED
Object Odia retelling of the Ramayana C17402 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: Odia retelling of the Ramayana
Context triple: [Vilanka Ramayana, instanceOf, Odia retelling of the Ramayana]
  • A. adaptation of the Ramayana chosen
    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.
  • B. Ramayana adaptation
    A Ramayana adaptation is a creative reinterpretation of the ancient Indian epic that reshapes its characters, plot, themes, or setting to resonate with a new cultural, temporal, or artistic context while retaining its core narrative essence.
  • C. retelling of the Mahabharata
    A retelling of the Mahabharata is a reimagined narrative of the ancient Indian epic that preserves its core characters, events, and themes while adapting the story’s perspective, style, or context for a new audience.
  • 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. 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.
  • 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
Created at: April 16, 2026, 8:45 p.m.