Triple
T29182019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149 |
E739767
|
entity |
| Predicate | hasToneFrequencyResolution |
P180522
|
FINISHED |
| Object | 12-bit period value |
—
|
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: 12-bit period value | Statement: [Yamaha YM2149, hasToneFrequencyResolution, 12-bit period value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasToneFrequencyResolution Context triple: [Yamaha YM2149, hasToneFrequencyResolution, 12-bit period value]
-
A.
hasToneFunction
Indicates that one entity serves a specific tonal or harmonic function in relation to another entity within a musical context.
-
B.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
C.
hasTuningDivision
Indicates that one entity specifies or uses a particular system or scheme for dividing a range (such as a musical interval or scale) into tuning units.
-
D.
haveTone
Indicates that an entity possesses or exhibits a particular tone, such as a specific attitude, mood, or quality of expression.
-
E.
tonalFeatures
Indicates that one entity specifies or characterizes the tonal properties or qualities associated with another entity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 11:58 a.m.