Triple
T26926079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malavikagnimitram |
E677781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical Indian drama |
C43674
|
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: classical Indian drama Context triple: [Malavikagnimitram, instanceOf, classical Indian drama]
-
A.
Sanskrit theatre
chosen
Sanskrit theatre is a classical Indian dramatic tradition, rooted in ancient Sanskrit texts like the Nāṭyaśāstra, that combines stylized acting, music, dance, and poetic dialogue to depict mythological, heroic, and romantic themes within a highly codified aesthetic framework.
-
B.
Ankiya Naat
Ankiya Naat is a traditional Assamese one-act play form, created by the saint-scholar Srimanta Sankardeva, that combines devotional themes with music, dance, and dialogue to convey religious and moral teachings.
-
C.
Marathi musical play
A Marathi musical play is a theatrical performance in the Marathi language that integrates drama, dialogue, and live music—often including classical, folk, and devotional songs—to tell culturally rooted stories on stage.
-
D.
Bhojpuri theatre form
Bhojpuri theatre form is a regional dramatic tradition from the Bhojpuri-speaking areas of India and Nepal that blends folk music, dance, and storytelling to depict local life, social issues, and cultural values.
-
E.
Assamese devotional play
An Assamese devotional play is a traditional dramatic performance from Assam that combines music, dance, dialogue, and religious themes to depict stories from Hindu mythology and local spiritual traditions.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:09 a.m.