Triple
T10459000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus de Funk |
E246619
|
entity |
| Predicate | hasHarmonicCharacteristic |
P45796
|
FINISHED |
| Object | bebop-influenced harmony |
—
|
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: bebop-influenced harmony | Statement: [Opus de Funk, hasHarmonicCharacteristic, bebop-influenced harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarmonicCharacteristic Context triple: [Opus de Funk, hasHarmonicCharacteristic, bebop-influenced harmony]
-
A.
usesHarmonics
Indicates that one entity employs harmonic frequencies or overtones of another entity or signal as part of its operation or behavior.
-
B.
hasHarmony
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
C.
hasMusicCharacteristic
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
D.
hasNasalHarmony
Indicates that a phonological process causes nasality in one segment to spread to or be shared with other segments within a word or domain.
-
E.
hasMusicalStyleCharacteristic
chosen
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe4b6d408190af59104a44871578 |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:18 p.m.