Triple
T16500003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Come as You Are |
E400775
|
entity |
| Predicate | hasMainRiffType |
P22757
|
FINISHED |
| Object | guitar riff |
—
|
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: guitar riff | Statement: [Come as You Are, hasMainRiffType, guitar riff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainRiffType Context triple: [Come as You Are, hasMainRiffType, guitar riff]
-
A.
hasMainRiff
Indicates that one musical piece, section, or track features another musical phrase or pattern as its primary recurring riff.
-
B.
hasRiffType
chosen
Indicates that one entity is characterized by, or associated with, a specific type or category of riff.
-
C.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
D.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
E.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e35b96881908c9d339eea9e4314 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.