Triple
T24279635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Yaman |
E605503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindustani classical raga |
C33385
|
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: Hindustani classical raga Context triple: [Raga Yaman, instanceOf, Hindustani classical raga]
-
A.
Hindustani classical music gharana
A Hindustani classical music gharana is a stylistically distinct lineage or school of musical thought and practice, traditionally passed down through generations of guru–shishya (teacher–disciple) relationships.
-
B.
South Indian classical music
South Indian classical music, or Carnatic music, is a highly structured and devotional musical tradition characterized by intricate melodic frameworks (ragas), complex rhythmic cycles (talas), and improvisation rooted in ancient Hindu scriptures and South Indian cultural heritage.
-
C.
Hindustani classical musician
A Hindustani classical musician is an artist who performs, improvises, and interprets North Indian classical music within established ragas and talas, often through vocal or instrumental traditions.
-
D.
item in Indian classical performance
chosen
An item in an Indian classical performance is a distinct, self-contained piece or segment—such as a composition, raga presentation, or dance number—structured with its own theme, mood, and form within the overall concert or recital.
-
E.
North Indian folk tradition
North Indian folk tradition encompasses the region’s diverse, community-based music, dance, storytelling, and ritual practices that express local histories, beliefs, and everyday life.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:07 a.m.