Triple
T31049593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Love |
E791221
|
entity |
| Predicate | hasSignatureSongForArtist |
P7272
|
FINISHED |
| Object | My Love (song) |
—
|
NE NERFINISHED |
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: My Love (song) | Statement: [My Love, hasSignatureSongForArtist, My Love (song)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureSongForArtist Context triple: [My Love, hasSignatureSongForArtist, My Love (song)]
-
A.
hasSignatureSong
Indicates that an artist or performer is especially associated with a particular song that is widely recognized as their defining or most iconic work.
-
B.
isSignatureSongOf
chosen
Indicates that a particular song is widely recognized as the most iconic or defining song associated with a specific artist or group.
-
C.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
D.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
-
E.
hasNotableSongWithBand
Indicates that an artist or individual is associated with a band through a song that is considered notable or significant.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 9 p.m.