Triple
T26206870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Money for Nothing |
E655378
|
entity |
| Predicate | hasNotableSound |
P144957
|
FINISHED |
| Object | heavily processed guitar tone |
—
|
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: heavily processed guitar tone | Statement: [Money for Nothing, hasNotableSound, heavily processed guitar tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSound Context triple: [Money for Nothing, hasNotableSound, heavily processed guitar tone]
-
A.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
C.
notableSoundCharacteristic
chosen
Indicates a distinctive or noteworthy quality of the sound produced or associated with an entity.
-
D.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
-
E.
hasCatchySound
Indicates that something possesses an appealing, memorable, or attractive auditory quality.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 26, 2026, 8:51 p.m.