Triple
T10478074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sad Songs and Waltzes |
E247096
|
entity |
| Predicate | lyricalTopic |
P4921
|
FINISHED |
| Object | unmarketability of sad songs |
—
|
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: unmarketability of sad songs | Statement: [Sad Songs and Waltzes, lyricalTopic, unmarketability of sad songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalTopic Context triple: [Sad Songs and Waltzes, lyricalTopic, unmarketability of sad songs]
-
A.
lyricalMotive
Indicates a recurring musical or textual idea that serves as a unifying expressive element within a lyrical or vocal work.
-
B.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
C.
lyricType
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
-
D.
hasLyricalTheme
chosen
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
E.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509596a088190895199648ccf91a4 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:21 p.m.