Triple
T35265336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worst Behavior |
E1018496
|
entity |
| Predicate | notableLyricFeature |
P9125
|
FINISHED |
| Object | repetitive hook |
—
|
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: repetitive hook | Statement: [Worst Behavior, notableLyricFeature, repetitive hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLyricFeature Context triple: [Worst Behavior, notableLyricFeature, repetitive hook]
-
A.
notableSongCharacteristic
chosen
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
B.
notableLyricReference
Indicates that one entity contains a significant or well-known reference to the lyrics of another entity (such as a song or musical work).
-
C.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
D.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
-
E.
notableLyricist
Indicates that the subject is a lyricist who is particularly distinguished or well-known for their work.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.