Triple
T22292802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katyar Kaljat Ghusli |
E551039
|
entity |
| Predicate | usesRaga |
P71747
|
FINISHED |
| Object | various Hindustani 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: various Hindustani ragas | Statement: [Katyar Kaljat Ghusli, usesRaga, various Hindustani ragas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRaga Context triple: [Katyar Kaljat Ghusli, usesRaga, various Hindustani ragas]
-
A.
hasRaga
chosen
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
B.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
C.
hasRitualMusic
Indicates that one entity is associated with or characterized by ritual music used in formal or ceremonial practices.
-
D.
usesVocalInstrument
Indicates that an entity performs or produces sound using their voice as a musical instrument.
-
E.
usesMusicalSystem
Indicates that one entity employs or operates according to a particular musical system, framework, or set of musical rules.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560d1ec48190ab86f158c94b677b |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.