Triple
T24378998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Todi |
E614557
|
entity |
| Predicate | usesSwaras |
P155983
|
FINISHED |
| Object | Sa Re Ga Ma Pa Dha Ni Sa |
—
|
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: Sa Re Ga Ma Pa Dha Ni Sa | Statement: [Raga Todi, usesSwaras, Sa Re Ga Ma Pa Dha Ni Sa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSwaras Context triple: [Raga Todi, usesSwaras, Sa Re Ga Ma Pa Dha Ni Sa]
-
A.
usesSyllables
Indicates that one entity forms, expresses, or analyzes something by employing syllables as its basic units.
-
B.
hasGranthaConsonants
Indicates that an entity includes or makes use of consonant characters from the Grantha script.
-
C.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
D.
hasMatrasPerVibhag
Indicates a relationship where each vibhag (metrical division) is associated with a specific number of matras (time units) it contains.
-
E.
hasVirama
Indicates that a character or script element is associated with a virama sign, typically used to suppress the inherent vowel or join consonants in abugida writing systems.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293da489c81909a7912b790be8b8a |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:02 a.m.