Triple
T8176706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigerian |
E190952
|
entity |
| Predicate | associatedWithMusicGenres |
P5149
|
FINISHED |
| Object | Afrobeats |
—
|
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: Afrobeats | Statement: [Nigerian, associatedWithMusicGenres, Afrobeats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMusicGenres Context triple: [Nigerian, associatedWithMusicGenres, Afrobeats]
-
A.
genreAssociatedWith
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
-
B.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
C.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
-
D.
knownForMusicGenre
chosen
Indicates that an entity is recognized or notable for producing, performing, or being associated with a particular music genre.
-
E.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4aba0dd88190828080d0d89612eb |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.