Triple

T25255954
Position Surface form Disambiguated ID Type / Status
Subject Andhra Mahabharatam E633173 entity
Predicate instanceOf P0 FINISHED
Object Mahabharata adaptation C20602 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: Mahabharata adaptation
Context triple: [Andhra Mahabharatam, instanceOf, Mahabharata adaptation]
  • A. adaptation of the Mahabharata chosen
    An adaptation of the Mahabharata is a creative reinterpretation of the ancient Indian epic’s characters, themes, and narratives into a new medium, context, or perspective while retaining its core moral and philosophical essence.
  • 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. 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.
  • D. Mahabharata reteller
    A Mahabharata reteller is a storyteller who reinterprets and narrates the epic Mahabharata for contemporary audiences, adapting its characters, events, and themes while preserving its core essence.
  • E. 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.
  • 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_69e75a922ad481908f4f1f884583cb42 completed April 21, 2026, 11:08 a.m.
Created at: April 21, 2026, 1:13 p.m.