Triple
T11201782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahasa Bhima Vijaya |
E265057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mahabharata-based literary work |
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-based literary work Context triple: [Sahasa Bhima Vijaya, instanceOf, Mahabharata-based literary work]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
ancient literary work
An ancient literary work is a written composition created in antiquity that reflects the language, culture, beliefs, and artistic expression of early civilizations.
-
E.
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.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:29 p.m.