Triple
T19861884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edge of Seventeen |
E477284
|
entity |
| Predicate | hasVocalHook |
P79253
|
FINISHED |
| Object | distinctive vocal 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: distinctive vocal hook | Statement: [Edge of Seventeen, hasVocalHook, distinctive vocal hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalHook Context triple: [Edge of Seventeen, hasVocalHook, distinctive vocal hook]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
hasChorusHook
chosen
Indicates that a musical work features a prominent, recurring chorus section that serves as a memorable hook.
-
C.
hasVocalProcessing
Indicates that an entity’s vocal audio has been altered or enhanced through some form of signal processing.
-
D.
hasHookSinger
Indicates that one entity serves as the hook singer (performing the main recurring vocal refrain) for another entity, typically a song or musical track.
-
E.
hasBackwardVocals
Indicates that the subject uses or contains backward (reversed) vocal audio in relation to the object.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589b3cbc8190afe847e83f04c45b |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.