Triple
T19850083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everybody must get stoned |
E476968
|
entity |
| Predicate | lyricalFunction |
P137568
|
FINISHED |
| Object | hook line |
—
|
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: hook line | Statement: [Everybody must get stoned, lyricalFunction, hook line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalFunction Context triple: [Everybody must get stoned, lyricalFunction, hook line]
-
A.
lyricFunction
Indicates the role or purpose that a set of lyrics serves within a musical work or performance.
-
B.
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.
-
C.
lyricalEvent
Indicates an event or occurrence that is expressed, referenced, or described within the lyrics of a song.
-
D.
lyricalMotive
Indicates a recurring musical or textual idea that serves as a unifying expressive element within a lyrical or vocal work.
-
E.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65867b5408190bbd12ca567c4705f |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.