Triple
T30517893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149F |
E776613
|
entity |
| Predicate | hasNoiseChannelCount |
P82796
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Yamaha YM2149F, hasNoiseChannelCount, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoiseChannelCount Context triple: [Yamaha YM2149F, hasNoiseChannelCount, 1]
-
A.
supportsNoiseChannel
Indicates that one entity is capable of handling, transmitting, or operating with a specified noise channel in a system or process.
-
B.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
-
C.
hasChannelCount
chosen
Indicates that an entity is associated with a specific number of channels.
-
D.
hasNoiseFrequencyControl
Indicates that an entity provides a control or setting to adjust the frequency characteristics of noise.
-
E.
hasNumberOfADPCMAChannels
Indicates the quantity of ADPCM (Adaptive Differential Pulse-Code Modulation) channels associated with or supported by an entity.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: April 29, 2026, 8:16 p.m.