Triple
T31692796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goula |
E808836
|
entity |
| Predicate | commonTalaForMajorKriti |
P172055
|
FINISHED |
| Object | Adi tala |
—
|
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: Adi tala | Statement: [Goula, commonTalaForMajorKriti, Adi tala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTalaForMajorKriti Context triple: [Goula, commonTalaForMajorKriti, Adi tala]
-
A.
isMostCommonTala
chosen
Indicates that a given tāla (rhythmic cycle) is the most frequently used or prevalent among a set of tālas.
-
B.
musicalGharana
Indicates a stylistic lineage or school within a musical tradition to which an artist, performance, or composition belongs.
-
C.
basedOnRaga
Indicates that something (such as a composition, performance, or musical element) is derived from, structured around, or primarily influenced by a particular raga.
-
D.
isFoundationalRaga
Indicates that a raga serves as a primary or fundamental melodic framework upon which other ragas or musical structures are based.
-
E.
usesShuddhaSwaras
Indicates that an entity employs only the pure (shuddha) notes of the scale, without incorporating altered or variant swaras.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 30, 2026, 11:09 p.m.