Triple
T20135777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suka |
E491021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bhagavata Purana character |
C42239
|
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: Bhagavata Purana character Context triple: [Suka, instanceOf, Bhagavata Purana character]
-
A.
Character in the Ramayana
A Character in the Ramayana is an individual—divine, human, or demonic—whose actions, relationships, and moral choices drive the epic’s narrative and embody its spiritual and ethical teachings.
-
B.
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.
-
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.
entity in Indian epic tradition
chosen
An entity in the Indian epic tradition is any person, creature, deity, or supernatural being that participates in the narrative, cosmology, or moral framework of epics like the Mahābhārata and Rāmāyaṇa.
-
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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:32 p.m.