Triple
T31657671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Shoulder |
E807900
|
entity |
| Predicate | songBecomes |
P172076
|
FINISHED |
| Object | radio hit |
—
|
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: radio hit | Statement: [Low Shoulder, songBecomes, radio hit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songBecomes Context triple: [Low Shoulder, songBecomes, radio hit]
-
A.
songBecame
Indicates that one song transformed into, evolved into, or was reissued as another song, marking a change in its identity or version over time.
-
B.
basedOnSongFrom
Indicates that one creative work is derived from, adapted from, or otherwise based on a particular song.
-
C.
basedOnSongBy
Indicates that one entity is derived from, adapted from, or otherwise created using a particular song as its source or inspiration.
-
D.
coveredSongBy
Indicates that one musical work is a cover version performed or recorded by an artist of a song originally created or popularized by another artist.
-
E.
releasedSong
Indicates that an artist or entity has made a particular song publicly available, typically as a publication or distribution event.
- F. None of above. chosen
Provenance (4 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:56 p.m.