Triple
T20352979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krishna and Gandhari |
E496063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mahabharata relationship |
C43694
|
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 relationship Context triple: [Krishna and Gandhari, instanceOf, Mahabharata relationship]
-
A.
character group in the Mahabharata
A character group in the Mahabharata is a set of individuals—such as families, factions, or allied kingdoms—linked by kinship, loyalty, or shared purpose, whose collective actions and relationships drive the epic’s narrative and moral conflicts.
-
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.
Mahabharata episode
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.
-
D.
MahabharataCharacter
A MahabharataCharacter represents an individual entity from the Indian epic Mahabharata, encapsulating their identity, lineage, allegiances, roles in key events, relationships, and associated attributes such as virtues, flaws, and divine connections.
-
E.
Mughal–Rajput relations
Mughal–Rajput relations refer to the complex web of political alliances, military conflicts, matrimonial ties, and cultural exchanges between the Mughal Empire and the Rajput kingdoms of northern and western India from the 16th to 18th centuries.
- F. None of above. chosen
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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:25 a.m.