Triple
T27947800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goody Bag |
E703335
|
entity |
| Predicate | belongsToMusicCulture |
P151586
|
FINISHED |
| Object | Afrobeats era of 2010s Nigeria |
—
|
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 era of 2010s Nigeria | Statement: [Goody Bag, belongsToMusicCulture, Afrobeats era of 2010s Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToMusicCulture Context triple: [Goody Bag, belongsToMusicCulture, Afrobeats era of 2010s Nigeria]
-
A.
inMusicCulture
chosen
Indicates that something is part of, associated with, or situated within a particular music-related cultural context or tradition.
-
B.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
C.
collectionIncludesCulture
Indicates that a collection contains, represents, or is associated with a particular culture.
-
D.
cultureRelatedTo
Indicates a relationship where one entity is connected, associated, or relevant to the culture, traditions, or cultural context of another entity.
-
E.
associatedWithMusicScene
Indicates a relationship where an entity is connected or linked to a particular music scene, culture, or community.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 7:23 p.m.