Triple
T20352904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yudhishthira and Gandhari |
E496062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mahabharata characters pairing |
C20798
|
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 characters pairing Context triple: [Yudhishthira and Gandhari, instanceOf, Mahabharata characters pairing]
-
A.
character-actor pairing
A character-actor pairing represents the association between a fictional character and the specific performer who portrays that character in a given production.
-
B.
literary character pair
chosen
A literary character pair is a duo of fictional individuals whose relationship, interactions, or contrasting traits are central to the development of a narrative’s themes and plot.
-
C.
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.
-
D.
Hindu legendary couple
A Hindu legendary couple is a pair of figures from Hindu mythology or epic tradition whose relationship embodies idealized virtues such as devotion, dharma, love, and sacrifice, often serving as moral and spiritual exemplars.
-
E.
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.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:25 a.m.