Triple
T30761347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishnupur |
E783243
|
entity |
| Predicate | hasMusicGharana |
P134272
|
FINISHED |
| Object | Bishnupur 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: Bishnupur gharana | Statement: [Bishnupur, hasMusicGharana, Bishnupur gharana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicGharana Context triple: [Bishnupur, hasMusicGharana, Bishnupur gharana]
-
A.
musicalGharana
Indicates a stylistic lineage or school within a musical tradition to which an artist, performance, or composition belongs.
-
B.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
C.
associatedWithGharana
chosen
Indicates a relationship where an entity is linked or connected to a particular gharana (a specific musical or artistic lineage or school).
-
D.
hasMusicInstitution
Indicates that an entity is associated with or hosts a music-related institution, such as a conservatory, music school, or similar organization.
-
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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 8:39 p.m.