Triple
T32738484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shake N’ Stomp |
E837154
|
entity |
| Predicate | guitarTechniqueShowcased |
P150227
|
FINISHED |
| Object | tremolo picking |
—
|
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: tremolo picking | Statement: [Shake N’ Stomp, guitarTechniqueShowcased, tremolo picking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guitarTechniqueShowcased Context triple: [Shake N’ Stomp, guitarTechniqueShowcased, tremolo picking]
-
A.
musicalTechniques
Indicates the specific methods or approaches used to create, shape, or perform music in relation to an entity.
-
B.
notableInstrumentTechnique
Indicates that an entity is particularly recognized for using, developing, or being associated with a specific musical instrument technique.
-
C.
demonstratedTechniqueFocus
chosen
Indicates that an entity has shown or highlighted a particular technique as the main focus of its demonstration.
-
D.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
E.
isGuitarDriven
Indicates that something (such as a song, piece of music, or performance) is primarily led, dominated, or characterized by the sound and role of the guitar.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c905c12c81908e40ddbd065ff441 |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f717a88190a924d614c2c9bca3 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:12 a.m.