Triple
T480638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afrobeats |
E9158
|
entity |
| Predicate | musicFusionOf |
P14839
|
FINISHED |
| Object | traditional African rhythms |
—
|
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: traditional African rhythms | Statement: [Afrobeats, musicFusionOf, traditional African rhythms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicFusionOf Context triple: [Afrobeats, musicFusionOf, traditional African rhythms]
-
A.
musicBy
Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
-
B.
musicDriven
Indicates that one entity’s behavior, structure, or progression is guided, influenced, or determined primarily by music or musical elements.
-
C.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
D.
musicKey
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
E.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f058ebe48190aaa0a829b21f75fa |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef4030608190b39852b347a505ca |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.