Triple
T6400681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombtrack |
E144052
|
entity |
| Predicate | hasRiffStyle |
P22757
|
FINISHED |
| Object | drop-D tuned guitar |
—
|
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: drop-D tuned guitar | Statement: [Bombtrack, hasRiffStyle, drop-D tuned guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiffStyle Context triple: [Bombtrack, hasRiffStyle, drop-D tuned guitar]
-
A.
hasRiffType
chosen
Indicates that one entity is characterized by, or associated with, a specific type or category of riff.
-
B.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
C.
hasMainRiff
Indicates that one musical piece, section, or track features another musical phrase or pattern as its primary recurring riff.
-
D.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
E.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0689ae99881909ba427769fd317ae |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.