Triple
T13713777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kbandu drum |
E328839
|
entity |
| Predicate | relativePitch |
P111287
|
FINISHED |
| Object | lower-pitched than playing drum |
—
|
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: lower-pitched than playing drum | Statement: [Kbandu drum, relativePitch, lower-pitched than playing drum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePitch Context triple: [Kbandu drum, relativePitch, lower-pitched than playing drum]
-
A.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
B.
pitchConvertedTo
Indicates that one pitch has been transformed or translated into another pitch or pitch representation.
-
C.
stripPitch
Indicates removing the pitch or tonal information from an audio signal or sound representation, leaving only non-pitch-related characteristics.
-
D.
locationRelativeToPitch
Indicates the spatial position of an entity in relation to the pitch (e.g., above, beside, or within the pitch area).
-
E.
tonalCenter
Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
- F. None of above. chosen
Provenance (4 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43973cf08190a417d0cca9dd314a |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.