Triple
T36330258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knock on Wood |
E894623
|
entity |
| Predicate | followsMusicalStyleOf |
P151151
|
FINISHED |
| Object | Memphis soul |
—
|
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: Memphis soul | Statement: [Knock on Wood, followsMusicalStyleOf, Memphis soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsMusicalStyleOf Context triple: [Knock on Wood, followsMusicalStyleOf, Memphis soul]
-
A.
hasMusicalStyleSimilarTo
Indicates that two entities share a comparable or closely related musical style or sound.
-
B.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
C.
playsInStyleOf
chosen
Indicates that one entity performs, creates, or behaves in a manner characteristic of another entity’s style.
-
D.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
E.
includesMusicalStyle
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
- 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.