Triple
T29101417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YMF276 |
E736647
|
entity |
| Predicate | supportsRhythmMode |
P112024
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yamaha YMF276, supportsRhythmMode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRhythmMode Context triple: [Yamaha YMF276, supportsRhythmMode, true]
-
A.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
B.
featuresRhythm
chosen
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
-
C.
hasRhythmicComplexity
Indicates that one entity exhibits or involves a level of rhythmic intricacy or variation in relation to another entity or context.
-
D.
supportsMIDI
Indicates that one entity provides compatibility with or the ability to use MIDI (Musical Instrument Digital Interface) functionality for another entity.
-
E.
hasRhythmicOrigin
Indicates that something originates from, is derived from, or is fundamentally based on rhythm or rhythmic patterns.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0302d9d2d88190b20429530775b035 |
completed | May 12, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_6a0302289128819085428f3d544c2fb9 |
completed | May 12, 2026, 10:34 a.m. |
Created at: April 28, 2026, 11:12 a.m.