Triple
T29540149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masattuvan |
E749469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Silappatikaram character |
C24831
|
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: Silappatikaram character Context triple: [Masattuvan, instanceOf, Silappatikaram character]
-
A.
character in Silappatikaram
chosen
A character in Silappatikaram is an individual—mortal, divine, or symbolic—whose actions, relationships, and moral choices drive the epic’s exploration of justice, fate, and dharma in ancient Tamil society.
-
B.
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.
-
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.
character in Kakawin Sutasoma
A character in Kakawin Sutasoma is an entity—divine, human, or mythical—who participates in the narrative of the Old Javanese Buddhist kakawin, contributing to its themes of morality, unity, and spiritual enlightenment.
-
E.
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.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:02 p.m.