Triple
T30661374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doing It to Death |
E780538
|
entity |
| Predicate | hasNotableGroove |
P34397
|
FINISHED |
| Object | iconic funk groove |
—
|
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: iconic funk groove | Statement: [Doing It to Death, hasNotableGroove, iconic funk groove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGroove Context triple: [Doing It to Death, hasNotableGroove, iconic funk groove]
-
A.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
-
B.
hasLaidBackGroove
chosen
Indicates that something (typically music or a performance) features a relaxed, unhurried rhythmic feel or vibe.
-
C.
hasNotableBassline
Indicates that something (typically a piece of music) features a bassline that is particularly prominent, distinctive, or otherwise noteworthy.
-
D.
hasNotableDrumBreak
Indicates that a musical work contains a drum segment that is particularly prominent, distinctive, or widely recognized.
-
E.
hasDistinctiveRiff
Indicates that something features a unique, recognizable musical phrase or pattern that sets it apart from others.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: April 29, 2026, 8:31 p.m.