Triple
T2354541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Road Again |
E47523
|
entity |
| Predicate | mainLyricMotive |
P7609
|
FINISHED |
| Object | joy of being on tour again |
—
|
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: joy of being on tour again | Statement: [On the Road Again, mainLyricMotive, joy of being on tour again]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLyricMotive Context triple: [On the Road Again, mainLyricMotive, joy of being on tour again]
-
A.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
B.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
C.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
D.
lyricSetting
Indicates that one entity serves as the text or lyrics that are set to music or otherwise musically realized by another entity.
-
E.
hasLyricsTheme
chosen
Indicates that the lyrics of a work primarily concern or revolve around a specified theme or subject.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.