Triple
T19198710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Worried Man |
E470041
|
entity |
| Predicate | lyricText |
P134835
|
FINISHED |
| Object | It takes a worried man to sing a worried song |
—
|
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: It takes a worried man to sing a worried song | Statement: [A Worried Man, lyricText, It takes a worried man to sing a worried song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricText Context triple: [A Worried Man, lyricText, It takes a worried man to sing a worried song]
-
A.
lyricType
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
-
B.
lyricFunction
Indicates the role or purpose that a set of lyrics serves within a musical work or performance.
-
C.
lyricSetting
Indicates that one entity serves as the text or lyrics that are set to music or otherwise musically realized by another entity.
-
D.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
E.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of another entity.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a8daac8190b3558a1388596fb0 |
completed | April 20, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.