Triple
T37100825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagomba |
E918696
|
entity |
| Predicate | traditionalMusicianTitle |
P131568
|
FINISHED |
| Object | lunsi |
—
|
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: lunsi | Statement: [Dagomba, traditionalMusicianTitle, lunsi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMusicianTitle Context triple: [Dagomba, traditionalMusicianTitle, lunsi]
-
A.
traditionalPerformer
Indicates that an entity performs or practices traditional, culturally inherited arts, rituals, or performances.
-
B.
traditionalInstrument
Indicates that an entity is a musical instrument associated with the traditional or customary music of a particular culture, region, or community.
-
C.
typeOfMusicProfessional
chosen
Indicates the specific professional role or occupation someone holds within the field of music.
-
D.
occupationInMusical
Indicates that an entity holds a specific occupation or role within the context of a musical work or production.
-
E.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.