Triple
T19595517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bāl Kāṇḍ |
E470338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of Ramcharitmanas |
C16619
|
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: section of Ramcharitmanas Context triple: [Bāl Kāṇḍ, instanceOf, section of Ramcharitmanas]
-
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.
kanda of the Ramayana
chosen
The kanda of the Ramayana is a major book or section of the epic, each focusing on a distinct phase of Lord Rama’s life and the unfolding of the narrative.
-
C.
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.
-
D.
Ramayana recension
A Ramayana recension is a distinct textual version or tradition of the Ramayana epic, characterized by its own set of variations in content, structure, language, and interpretation.
-
E.
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.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.