Triple

T29182004
Position Surface form Disambiguated ID Type / Status
Subject Yamaha YM2149 E739767 entity
Predicate hasVolumeControlPerChannel P86392 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 YM2149, hasVolumeControlPerChannel, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVolumeControlPerChannel
Context triple: [Yamaha YM2149, hasVolumeControlPerChannel, true]
  • A. supportsVolumeControl chosen
    Indicates that one entity provides the capability to adjust or manage the audio volume level of another entity.
  • B. hasNumberOfAmplifierChannels
    Indicates the relationship that specifies how many amplifier channels are present or supported in the associated entity.
  • C. surroundSoundChannelSupport
    Indicates that an audio device or system supports output through multiple discrete surround sound channels (e.g., 5.1, 7.1).
  • D. supportsAudioReturnChannel
    Indicates that one entity is capable of handling an audio return channel from another entity, allowing audio to be sent back over the same connection.
  • E. hasSpeechLevels
    Indicates that a language, dialect, or communicative system distinguishes different levels or styles of speech used according to social context, formality, or relative status between speakers.
  • 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_69f07cb74c2c8190ad396487fcb4fde6 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6bbf6e33c819086e5176d64e7a614 completed May 3, 2026, 3:07 a.m.
PD Predicate disambiguation batch_69f6ba6b1e6c8190adf9d6a257e0b744 completed May 3, 2026, 3 a.m.
Created at: April 28, 2026, 11:58 a.m.