Triple
T3086524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superstition |
E64384
|
entity |
| Predicate | hasMusicalStyleCharacteristic |
P45796
|
FINISHED |
| Object | syncopated 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: syncopated groove | Statement: [Superstition, hasMusicalStyleCharacteristic, syncopated groove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalStyleCharacteristic Context triple: [Superstition, hasMusicalStyleCharacteristic, syncopated groove]
-
A.
hasSongStyle
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
-
B.
includesMusicalStyle
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
E.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1ec187c819084565514ebb99cdb |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.