Triple
T28963381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Child o' Mine |
E731970
|
entity |
| Predicate | guitarRiffRecognition |
P70921
|
FINISHED |
| Object | widely acclaimed |
—
|
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: widely acclaimed | Statement: [Sweet Child o' Mine, guitarRiffRecognition, widely acclaimed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guitarRiffRecognition Context triple: [Sweet Child o' Mine, guitarRiffRecognition, widely acclaimed]
-
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.
hasGuitarRecognition
Indicates that an entity has received recognition, awards, or notable acknowledgment specifically for guitar performance or related guitar achievements.
-
C.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
D.
notableRiff
chosen
Indicates that an entity is recognized for having a distinctive, memorable, or influential musical riff associated with it.
-
E.
songRecognition
Indicates that an entity identifies or acknowledges a song, typically by matching it to a known title, artist, or recording.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65c2ae94c8190a6a524800686ef66 |
completed | May 2, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:51 a.m.