Triple
T24687891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Darbari Kanada |
E611347
|
entity |
| Predicate | usesShuddhaSwaras |
P157179
|
FINISHED |
| Object | shuddha Re |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: shuddha Re | Statement: [Raga Darbari Kanada, usesShuddhaSwaras, shuddha Re]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesShuddhaSwaras Context triple: [Raga Darbari Kanada, usesShuddhaSwaras, shuddha Re]
-
A.
usesSwaras
Indicates that one entity employs or incorporates specific musical notes (swaras) in relation to another entity or context.
-
B.
isConsideredShuddhaRaga
Indicates that a raga is regarded as a pure, fundamental, or primary raga within a given musical tradition.
-
C.
isFoundationalRaga
Indicates that a raga serves as a primary or fundamental melodic framework upon which other ragas or musical structures are based.
-
D.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
E.
hasGranthaConsonants
Indicates that an entity includes or makes use of consonant characters from the Grantha script.
- F. None of above. chosen
Provenance (4 batches)
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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 3:19 a.m.