Triple
T14046043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keep Away |
E337957
|
entity |
| Predicate | hasBassStyle |
P61997
|
FINISHED |
| Object | distorted bass |
—
|
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: distorted bass | Statement: [Keep Away, hasBassStyle, distorted bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBassStyle Context triple: [Keep Away, hasBassStyle, distorted bass]
-
A.
bassStyle
chosen
Indicates the characteristic manner or technique in which a bass part is played or written in relation to other musical elements.
-
B.
hasBassIntroBy
Indicates a relationship where a musical piece features an introductory section performed or led by a bass instrument or bass player.
-
C.
hasBassist
Indicates that an entity (typically a musical group or band) has another entity serving in the role of its bassist.
-
D.
hasNotableBassline
Indicates that something (typically a piece of music) features a bassline that is particularly prominent, distinctive, or otherwise noteworthy.
-
E.
hasGuitarStyle
Indicates that an entity is associated with, characterized by, or performs using a particular style of guitar playing.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312df37081909f45ce3e219af5dc |
completed | April 14, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.