Triple
T24181834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akan highlife |
E599445
|
entity |
| Predicate | usesMelodicElementsFrom |
P60129
|
FINISHED |
| Object | Akan folk songs |
—
|
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: Akan folk songs | Statement: [Akan highlife, usesMelodicElementsFrom, Akan folk songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMelodicElementsFrom Context triple: [Akan highlife, usesMelodicElementsFrom, Akan folk songs]
-
A.
hasMoreMelodicSoundThan
Indicates that the sound produced by one entity is judged to be more melodic, tuneful, or musically pleasing than the sound produced by another entity.
-
B.
isMelodic
Indicates that something possesses a tuneful, harmonious, or musically pleasing quality.
-
C.
hasMelodicOrchestration
Indicates that one entity provides or features the melodic orchestration for, or in association with, another entity.
-
D.
usesMusicalElement
chosen
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
E.
hasMelodyInstrument
Indicates that something uses or features a particular instrument to carry the main melody.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.