Triple
T14957828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happily Ever After (song) |
E372977
|
entity |
| Predicate | lyricalQuality |
P9652
|
FINISHED |
| Object | witty wordplay |
—
|
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: witty wordplay | Statement: [Happily Ever After (song), lyricalQuality, witty wordplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalQuality Context triple: [Happily Ever After (song), lyricalQuality, witty wordplay]
-
A.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
B.
hasLyricalStyle
chosen
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
C.
lyricalMood
Indicates the prevailing emotional tone or atmosphere conveyed through lyrics or vocal expression in a piece of music.
-
D.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
E.
hasLyricalRegister
Indicates that something (such as a text, utterance, or expression) is associated with a particular lyrical or stylistic register in language.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cd85bc81909040b7ff78f62554 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.