Triple
T31645238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabhi |
E807567
|
entity |
| Predicate | janyaRagaOf |
P155833
|
FINISHED |
| Object | Shankarabharanam |
—
|
NE NERFINISHED |
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: Shankarabharanam | Statement: [Arabhi, janyaRagaOf, Shankarabharanam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: janyaRagaOf Context triple: [Arabhi, janyaRagaOf, Shankarabharanam]
-
A.
basedOnRaga
Indicates that something (such as a composition, performance, or musical element) is derived from, structured around, or primarily influenced by a particular raga.
-
B.
isFoundationalRaga
Indicates that a raga serves as a primary or fundamental melodic framework upon which other ragas or musical structures are based.
-
C.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
D.
relatedRaga
chosen
Indicates that one raga is musically or structurally connected to another, such as through shared scales, motifs, or derivation.
-
E.
isConsideredShuddhaRaga
Indicates that a raga is regarded as a pure, fundamental, or primary raga within a given musical tradition.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a91e4f4c8190831089d81f5f0026 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:50 p.m.