Triple
T20129843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaksha Prashna |
E490859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | episode of the Mahabharata |
C42215
|
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: episode of the Mahabharata Context triple: [Yaksha Prashna, instanceOf, episode of the Mahabharata]
-
A.
Mahabharata episode
chosen
A Mahabharata episode is a distinct narrative unit within the epic that encapsulates a specific event, conflict, or teaching involving its characters and overarching themes.
-
B.
parva of the Mahābhārata
The parva of the Mahābhārata is a major structural division or "book" of the epic, each comprising a thematically unified sequence of chapters and episodes that together organize the narrative into 18 primary sections.
-
C.
book of the Mahābhārata
A book of the Mahābhārata is a major division of the epic that organizes its narrative, teachings, and episodes into a distinct, thematically coherent section of the larger work.
-
D.
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.
-
E.
event in the Kurukshetra War
An event in the Kurukshetra War is a distinct occurrence or incident—such as a battle, duel, divine intervention, or strategic decision—that takes place within the narrative timeline of the Kurukshetra conflict and influences its progression or outcome.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:31 p.m.