Triple
T6806178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otis Rush |
E156311
|
entity |
| Predicate | guitarPlayingStyle |
P26017
|
FINISHED |
| Object | played right-handed guitar upside down |
—
|
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: played right-handed guitar upside down | Statement: [Otis Rush, guitarPlayingStyle, played right-handed guitar upside down]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guitarPlayingStyle Context triple: [Otis Rush, guitarPlayingStyle, played right-handed guitar upside down]
-
A.
hasGuitarStyle
chosen
Indicates that an entity is associated with, characterized by, or performs using a particular style of guitar playing.
-
B.
primaryInstrumentalStyle
Indicates the main instrumental style or genre most closely associated with an entity’s musical performance or work.
-
C.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
D.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
E.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d3082dcc8190a84bc056236cc52e |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.