Triple
T36472452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keep On Loving You |
E898570
|
entity |
| Predicate | isDefiningSongOf |
P127261
|
FINISHED |
| Object | early 1980s rock radio |
—
|
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: early 1980s rock radio | Statement: [Keep On Loving You, isDefiningSongOf, early 1980s rock radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefiningSongOf Context triple: [Keep On Loving You, isDefiningSongOf, early 1980s rock radio]
-
A.
definingSongOf
chosen
Indicates that a particular song is regarded as the most characteristic, iconic, or representative piece associated with a given artist, group, or context.
-
B.
isSongIn
Indicates that a particular song is contained within or belongs to a specified collection, such as an album, playlist, or soundtrack.
-
C.
isForSong
Indicates that something is intended to be used with, associated with, or applicable to a particular song.
-
D.
isDefiningAnthemOf
Indicates that one entity serves as the official or primary anthem that represents or symbolizes another entity.
-
E.
isWorkSong
Indicates that the subject is a song specifically created for or associated with a particular work, job, or labor activity.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.