Triple
T21676006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoochie Coochie Man |
E534971
|
entity |
| Predicate | hasInfluentialRiff |
P145402
|
FINISHED |
| Object | stop-time 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: stop-time riff | Statement: [Hoochie Coochie Man, hasInfluentialRiff, stop-time riff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfluentialRiff Context triple: [Hoochie Coochie Man, hasInfluentialRiff, stop-time riff]
-
A.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
B.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
C.
hasAggressiveRiffs
Indicates that something features intense, forceful, or hard-edged musical riffs.
-
D.
hasMainRiff
Indicates that one musical piece, section, or track features another musical phrase or pattern as its primary recurring riff.
-
E.
hasInfluencedRepertoire
Indicates that one entity has had a significant impact on shaping, expanding, or modifying the range of works, pieces, or items regularly performed, used, or presented by another entity.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0f85748190944b9425ffed02ee |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:42 p.m.