Triple
T37236576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakoma ethnic group |
E923593
|
entity |
| Predicate | hasMusicTraditions |
P151586
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yakoma ethnic group, hasMusicTraditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicTraditions Context triple: [Yakoma ethnic group, hasMusicTraditions, yes]
-
A.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
B.
hasLivePerformanceTradition
Indicates that there exists an established custom or practice of performing the subject live, typically before an audience.
-
C.
inMusicCulture
chosen
Indicates that something is part of, associated with, or situated within a particular music-related cultural context or tradition.
-
D.
basedInGenreTradition
Indicates that something (such as a work or practice) is grounded in, follows, or is shaped by the conventions and traditions of a particular genre.
-
E.
hasFolkGenre
Indicates that something belongs to, is categorized under, or is associated with the folk music 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:15 p.m.