Triple
T25758072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How Long Blues |
E648657
|
entity |
| Predicate | guitaristOnOriginalRecording |
P73540
|
FINISHED |
| Object | Scrapper Blackwell |
—
|
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: Scrapper Blackwell | Statement: [How Long Blues, guitaristOnOriginalRecording, Scrapper Blackwell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guitaristOnOriginalRecording Context triple: [How Long Blues, guitaristOnOriginalRecording, Scrapper Blackwell]
-
A.
guitaristOnRecording
chosen
Indicates that a person performed as a guitarist on a specific audio recording.
-
B.
hasGuitarist
Indicates that an entity has, employs, or is associated with a guitarist as part of it.
-
C.
originalBassist
Indicates that the subject is the first or founding bass player associated with the object (such as a band or musical group).
-
D.
previousGuitarist
Indicates that one entity formerly served as the guitarist for another entity, but no longer holds that role.
-
E.
associatedInstrumentalist
Indicates that an instrumentalist is connected to or involved with another entity, such as a work, performance, or recording, in a relevant musical role.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd847ee48190a32b6b618d66f22d |
completed | May 2, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 4:42 a.m.