Triple
T15927861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hard in da Paint |
E386247
|
entity |
| Predicate | percussionCharacteristic |
P93553
|
FINISHED |
| Object | stuttering hi-hats |
—
|
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: stuttering hi-hats | Statement: [Hard in da Paint, percussionCharacteristic, stuttering hi-hats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: percussionCharacteristic Context triple: [Hard in da Paint, percussionCharacteristic, stuttering hi-hats]
-
A.
percussionStyle
chosen
Indicates the specific manner or technique in which percussion is played or executed in a given context.
-
B.
percussion
Indicates that an entity produces sound by being struck, shaken, or otherwise hit, as in playing or functioning as a percussion instrument.
-
C.
notableInstrumentFeature
Indicates that an instrument is distinguished by a particular characteristic, quality, or component that is especially noteworthy or defining.
-
D.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
E.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.