Triple
T29253296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Colombia |
E741627
|
entity |
| Predicate | hasRegionalMusicGenre |
P111298
|
FINISHED |
| Object | cumbia |
—
|
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: cumbia | Statement: [Northern Colombia, hasRegionalMusicGenre, cumbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalMusicGenre Context triple: [Northern Colombia, hasRegionalMusicGenre, cumbia]
-
A.
musicGenreRegion
chosen
Indicates the association between a music genre and the geographic region where it originates, is most prevalent, or is culturally significant.
-
B.
hasPrimaryGenreRegion
Indicates that an entity’s main or dominant genre is associated with a particular geographic region.
-
C.
hasMusicalRegion
Indicates a relationship where a musical work, performance, or element is associated with a specific geographic or cultural region in terms of style, origin, or influence.
-
D.
hasFolkGenre
Indicates that something belongs to, is categorized under, or is associated with the folk music genre.
-
E.
hasMusicalEnsembleGenre
Indicates that a musical ensemble is associated with or performs in a particular musical genre.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: April 28, 2026, 12:35 p.m.