Triple
T3134996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumina |
E65505
|
entity |
| Predicate | hasMusicFeature |
P44121
|
FINISHED |
| Object | polyrhythmic drumming |
—
|
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: polyrhythmic drumming | Statement: [Kumina, hasMusicFeature, polyrhythmic drumming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicFeature Context triple: [Kumina, hasMusicFeature, polyrhythmic drumming]
-
A.
hasMusicCharacteristic
chosen
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
B.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
C.
hasCommonMusic
Indicates that two entities share at least one piece of music preference, interest, or item in common.
-
D.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
E.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada562540081908627950dd0b56a1e |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.