Triple
T24656622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaipur-Atrauli gharana |
E610408
|
entity |
| Predicate | associatedWithRagaType |
P157810
|
FINISHED |
| Object | compound ragas |
—
|
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: compound ragas | Statement: [Jaipur-Atrauli gharana, associatedWithRagaType, compound ragas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRagaType Context triple: [Jaipur-Atrauli gharana, associatedWithRagaType, compound ragas]
-
A.
associatedWithRagaType
chosen
Indicates that something has a connection or linkage to a particular raga type.
-
B.
relatedRaga
Indicates that one raga is musically or structurally connected to another, such as through shared scales, motifs, or derivation.
-
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.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
E.
parentRagaGroup
Indicates that one raga group is the immediate parent or higher-level grouping of another raga group in a hierarchical structure.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 2:34 a.m.