Triple
T18960149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It’s Five O’Clock Somewhere |
E463890
|
entity |
| Predicate | typicalSettingInLyrics |
P84624
|
FINISHED |
| Object | bar |
—
|
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: bar | Statement: [It’s Five O’Clock Somewhere, typicalSettingInLyrics, bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSettingInLyrics Context triple: [It’s Five O’Clock Somewhere, typicalSettingInLyrics, bar]
-
A.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
B.
scriptUsedInLyrics
Indicates that a particular writing system or script is used to write or represent the lyrics of a song or musical work.
-
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.
hasSettingInLyrics
chosen
Indicates that the lyrics of a work explicitly describe or reference a particular setting or location.
-
E.
lyricType
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d1d784819095f3f886d7c47175 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon