Triple
T25656561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sarod |
E643251
|
entity |
| Predicate | hasProminentGharana |
P134272
|
FINISHED |
| Object | Maihar gharana |
—
|
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: Maihar gharana | Statement: [sarod, hasProminentGharana, Maihar gharana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentGharana Context triple: [sarod, hasProminentGharana, Maihar gharana]
-
A.
associatedWithGharana
chosen
Indicates a relationship where an entity is linked or connected to a particular gharana (a specific musical or artistic lineage or school).
-
B.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
C.
hasShikharaStyle
Indicates that a temple or structure possesses or is built in a specific shikhara (tower or spire) architectural style.
-
D.
hasGandharam
Indicates a relationship where one entity possesses, is associated with, or includes a gandharam (a specific musical note or tonal element) in relation to another entity.
-
E.
isFoundationalRaga
Indicates that a raga serves as a primary or fundamental melodic framework upon which other ragas or musical structures are based.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 21, 2026, 6:34 p.m.