Triple
T38440187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mricchakatika (Kannada adaptations) |
E906465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kannada-language adaptations |
C29225
|
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: Kannada-language adaptations Context triple: [Mricchakatika (Kannada adaptations), instanceOf, Kannada-language adaptations]
-
A.
Ramayana adaptation
A Ramayana adaptation is a creative reinterpretation of the ancient Indian epic that reshapes its characters, plot, themes, or setting to resonate with a new cultural, temporal, or artistic context while retaining its core narrative essence.
-
B.
adaptation of the Mahabharata
An adaptation of the Mahabharata is a creative reinterpretation of the ancient Indian epic’s characters, themes, and narratives into a new medium, context, or perspective while retaining its core moral and philosophical essence.
-
C.
adaptation of the Ramayana
An adaptation of the Ramayana is a creative reinterpretation of the ancient Indian epic’s characters, themes, and narrative—often updated in form, setting, or perspective—while retaining its core storyline of Rama’s journey, exile, and battle against Ravana.
-
D.
Kannada-language book
chosen
A Kannada-language book is a written work in any genre whose primary text is composed in the Kannada language, intended for reading by Kannada-literate audiences.
-
E.
cinematic adaptation of a language
A cinematic adaptation of a language is a filmic representation that translates the structures, rhythms, and expressive nuances of a spoken or written language into visual, auditory, and narrative forms.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.