Triple
T30543839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daahoud |
E777354
|
entity |
| Predicate | hasHarmonicFeatures |
P48651
|
FINISHED |
| Object | secondary dominants |
—
|
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: secondary dominants | Statement: [Daahoud, hasHarmonicFeatures, secondary dominants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarmonicFeatures Context triple: [Daahoud, hasHarmonicFeatures, secondary dominants]
-
A.
usesHarmonics
Indicates that one entity employs harmonic frequencies or overtones of another entity or signal as part of its operation or behavior.
-
B.
hasTrackFeatures
Indicates that something possesses or is associated with specific track-related characteristics or attributes.
-
C.
hasHarmony
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
D.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
E.
hasHarmonicMinorVariant
Indicates that one musical element (such as a scale, key, or melody) has a corresponding form that is derived from or expressed in the harmonic minor variant.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:19 p.m.