Triple
T38141585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Your Own Way |
E952490
|
entity |
| Predicate | hasNotableGuitarSolo |
P59493
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Go Your Own Way, hasNotableGuitarSolo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGuitarSolo Context triple: [Go Your Own Way, hasNotableGuitarSolo, true]
-
A.
hasGuitarSolo
chosen
Indicates that an entity (such as a song or performance) contains or features a guitar solo.
-
B.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
C.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
D.
hasNotableSongFeature
Indicates that one entity (typically a song) includes a significant or noteworthy contribution, appearance, or characteristic involving another entity.
-
E.
hasBassSolo
Indicates that a musical piece, section, or performance includes a solo passage specifically played by the bass 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.