Triple
T27668978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cigarettes & Alcohol |
E697309
|
entity |
| Predicate | hasProminentRiffSimilarTo |
P81361
|
FINISHED |
| Object | Get It On |
—
|
NE NERFINISHED |
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: Get It On | Statement: [Cigarettes & Alcohol, hasProminentRiffSimilarTo, Get It On]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentRiffSimilarTo Context triple: [Cigarettes & Alcohol, hasProminentRiffSimilarTo, Get It On]
-
A.
hasDistinctiveRiff
Indicates that something features a unique, recognizable musical phrase or pattern that sets it apart from others.
-
B.
hasInfluentialRiff
Indicates that one musical riff has had a significant impact on or has strongly influenced another piece, style, or musician.
-
C.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
D.
hasNotableMelodicSimilarityTo
chosen
Indicates that one musical piece shares a clearly recognizable and significant similarity in melody with another.
-
E.
hasMusicalStyleSimilarTo
Indicates that two entities share a comparable or closely related musical style or sound.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:40 p.m.