Triple
T16555703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Hour |
E402193
|
entity |
| Predicate | hasNotableLyricDevice |
P104602
|
FINISHED |
| Object | irony |
—
|
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: irony | Statement: [Happy Hour, hasNotableLyricDevice, irony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLyricDevice Context triple: [Happy Hour, hasNotableLyricDevice, irony]
-
A.
lyricDevice
Indicates a relationship where a lyrical technique or stylistic device is employed within or by a piece of text, such as a song or poem.
-
B.
hasLyricalRegister
Indicates that something (such as a text, utterance, or expression) is associated with a particular lyrical or stylistic register in language.
-
C.
hasLyricsFeature
chosen
Indicates that something possesses a particular characteristic or attribute related to its lyrics.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc99f648190b40869ce52d351c8 |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.