Triple
T22166515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin trap |
E547801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgenre of trap music |
C31313
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: subgenre of trap music Context triple: [Latin trap, instanceOf, subgenre of trap music]
-
A.
techno subgenre
A techno subgenre is a stylistically distinct category within techno music defined by specific rhythmic patterns, sound design characteristics, tempo ranges, and cultural or regional influences.
-
B.
funk subgenre
A funk subgenre is a stylistically distinct branch of funk music characterized by its own specific rhythmic patterns, instrumentation, production techniques, and cultural influences while retaining funk’s core emphasis on groove and syncopation.
-
C.
regional style of hip hop
chosen
A regional style of hip hop is a distinct variation of the genre shaped by the cultural, linguistic, social, and musical influences of a specific geographic area, resulting in recognizable differences in sound, themes, and performance practices.
-
D.
soul music subgenre
A soul music subgenre is a stylistically distinct branch of soul that blends its core emotional vocals and groove-based rhythms with specific regional, cultural, or cross-genre influences to create a recognizable, cohesive sound identity.
-
E.
jazz subgenre
A jazz subgenre is a distinct stylistic branch of jazz music characterized by particular rhythmic feels, harmonic approaches, instrumentation, and cultural or historical contexts that differentiate it from other forms of jazz.
- F. None of above.
Provenance (1 batch)
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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:34 p.m.