Triple
T6502310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scuttle Buttin' |
E148916
|
entity |
| Predicate | keyArtistRole |
P24740
|
FINISHED |
| Object | lead guitar by Stevie Ray Vaughan |
—
|
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: lead guitar by Stevie Ray Vaughan | Statement: [Scuttle Buttin', keyArtistRole, lead guitar by Stevie Ray Vaughan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyArtistRole Context triple: [Scuttle Buttin', keyArtistRole, lead guitar by Stevie Ray Vaughan]
-
A.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
B.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
C.
musicIndustryRole
Indicates the professional function or position an entity holds within the music industry ecosystem.
-
D.
primaryArtist
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
E.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:42 p.m.