Triple
T22724797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Many Men (Wish Death) |
E561959
|
entity |
| Predicate | hasHookVocalStyle |
P149465
|
FINISHED |
| Object | melodic, sung 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: melodic, sung hook | Statement: [Many Men (Wish Death), hasHookVocalStyle, melodic, sung hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHookVocalStyle Context triple: [Many Men (Wish Death), hasHookVocalStyle, melodic, sung hook]
-
A.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
B.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
C.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
D.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
-
E.
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.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17928a21c8190a1b888754ba7808b |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:20 p.m.