Triple
T7205540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Start Me Up |
E148655
|
entity |
| Predicate | hasOpeningRiff |
P61186
|
FINISHED |
| Object | iconic guitar riff by Keith Richards |
—
|
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: iconic guitar riff by Keith Richards | Statement: [Start Me Up, hasOpeningRiff, iconic guitar riff by Keith Richards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningRiff Context triple: [Start Me Up, hasOpeningRiff, iconic guitar riff by Keith Richards]
-
A.
hasMainRiff
chosen
Indicates that one musical piece, section, or track features another musical phrase or pattern as its primary recurring riff.
-
B.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
C.
hasOpeningLyric
Indicates that one entity serves as the opening lyric of another entity, typically a song or musical work.
-
D.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
E.
hasRhythmSection
Indicates that an entity (such as a musical group or piece) includes or is associated with a rhythm section component.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e94ef5cc81908c33adcedf5c5054 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.