Triple
T18601305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurdy Gurdy Man |
E454624
|
entity |
| Predicate | hasNotableGuitarWork |
P33590
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hurdy Gurdy Man, hasNotableGuitarWork, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGuitarWork Context triple: [Hurdy Gurdy Man, hasNotableGuitarWork, yes]
-
A.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
B.
hasDissonantGuitarWork
Indicates that the subject features guitar playing characterized by clashing, tense, or harmonically unstable sounds.
-
C.
hasNotableMusicWork
chosen
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
-
D.
hasGuitarist
Indicates that an entity has, employs, or is associated with a guitarist as part of it.
-
E.
hasMelodicGuitarWork
Indicates that something features prominent or notable guitar parts characterized by a clear, tuneful, and melodic playing style.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5475112608190acacc5ac7a08c4a0 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.