Triple
T24747931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Kafi |
E619053
|
entity |
| Predicate | hasKomalSvara |
P155983
|
FINISHED |
| Object | Ni |
—
|
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: Ni | Statement: [Raga Kafi, hasKomalSvara, Ni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKomalSvara Context triple: [Raga Kafi, hasKomalSvara, Ni]
-
A.
usesKomalRe
Indicates that one entity employs or incorporates the musical note Komal Re (flattened second) in relation to another entity or context.
-
B.
usesKomalDha
Indicates that one musical entity employs the flattened (komal) Dha note in relation to another entity or context.
-
C.
usesSwaras
chosen
Indicates that one entity employs or incorporates specific musical notes (swaras) in relation to another entity or context.
-
D.
hasVowelHarmony
Indicates that the phonological vowels in a word or morpheme conform to a systematic harmony pattern (e.g., all front or all back vowels) according to the language’s vowel harmony rules.
-
E.
hasNasalHarmony
Indicates that a phonological process causes nasality in one segment to spread to or be shared with other segments within a word or domain.
- F. None of above.
Provenance (3 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:23 a.m.