Triple
T20202434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harivamsa |
E493257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | appendix (khila) to the Mahabharata |
C40880
|
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: appendix (khila) to the Mahabharata Context triple: [Harivamsa, instanceOf, appendix (khila) to the Mahabharata]
-
A.
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.
-
B.
book of the Mahābhārata
chosen
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.
-
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.
Kalpasūtra
Kalpasūtra is a Jain canonical text, primarily of the Śvetāmbara tradition, that contains biographies of the Tīrthaṅkaras (especially Mahāvīra), rules for monastic conduct, and liturgical guidelines recited during the Paryuṣaṇa festival.
-
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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.