Triple
T34076077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabad |
E873910
|
entity |
| Predicate | musicallyRenderedIn |
P194715
|
FINISHED |
| Object | Raga |
—
|
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: Raga | Statement: [Shabad, musicallyRenderedIn, Raga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicallyRenderedIn Context triple: [Shabad, musicallyRenderedIn, Raga]
-
A.
musicalDepictionOf
Indicates that one entity is a musical work that artistically represents, portrays, or is inspired by another entity.
-
B.
hasFictionalMusicVideo
Indicates that a subject has an associated music video that exists only within a fictional or narrative context, rather than as a real-world production.
-
C.
sangSoundtrackFor
Indicates that one entity performed or recorded the soundtrack music for a work associated with another entity.
-
D.
isSoundtrackOf
Indicates that a piece of music or collection of music serves as the soundtrack for a particular work, such as a film, game, or show.
-
E.
isMusicalWorkFor
Indicates that a musical work is created, intended, or designated for a particular entity, such as an instrument, performer, event, or context.
- F. None of above. chosen
Provenance (4 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
| PDg | Predicate description generation | batch_69fd82ebe1c081908455fc45b6e45178 |
completed | May 8, 2026, 6:30 a.m. |
Created at: May 1, 2026, 1:52 a.m.