Triple
T4454124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jimi Hendrix Experience |
E97680
|
entity |
| Predicate | roleOfJimiHendrix |
P22146
|
FINISHED |
| Object | guitarist and lead vocalist |
—
|
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: guitarist and lead vocalist | Statement: [The Jimi Hendrix Experience, roleOfJimiHendrix, guitarist and lead vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfJimiHendrix Context triple: [The Jimi Hendrix Experience, roleOfJimiHendrix, guitarist and lead vocalist]
-
A.
hasGuitarist
Indicates that an entity has, employs, or is associated with a guitarist as part of it.
-
B.
Tom WilsonRole
Indicates that Tom has the role or position of Wilson in some context or system.
-
C.
notableBandMember
chosen
Indicates that the subject is a member of the band in the object and is recognized as particularly prominent or significant within that band.
-
D.
featuresMusician
Indicates that something (such as a work, event, or recording) prominently includes or showcases a particular musician.
-
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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f669948190b14ef42e8dbca525 |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.