Triple
T35705053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohemian Like You |
E1031695
|
entity |
| Predicate | hasCatchyGuitarRiff |
P172767
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bohemian Like You, hasCatchyGuitarRiff, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatchyGuitarRiff Context triple: [Bohemian Like You, hasCatchyGuitarRiff, true]
-
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.
hasDistinctiveRiff
chosen
Indicates that something features a unique, recognizable musical phrase or pattern that sets it apart from others.
-
D.
hasInfluentialRiff
Indicates that one musical riff has had a significant impact on or has strongly influenced another piece, style, or musician.
-
E.
hasRhythmGuitar
Indicates that an entity includes or features a rhythm guitar as part of its musical instrumentation or arrangement.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 3, 2026, 4:05 p.m.