Triple
T29181986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149 |
E739767
|
entity |
| Predicate | hasNumberOfSoundChannels |
P82796
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Yamaha YM2149, hasNumberOfSoundChannels, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfSoundChannels Context triple: [Yamaha YM2149, hasNumberOfSoundChannels, 3]
-
A.
hasChannelCount
chosen
Indicates that an entity is associated with a specific number of channels.
-
B.
hasNumberOfADPCMAChannels
Indicates the quantity of ADPCM (Adaptive Differential Pulse-Code Modulation) channels associated with or supported by an entity.
-
C.
audioChannels
Indicates the number or configuration of distinct audio signal paths (such as mono, stereo, or surround) used in a recording, transmission, or playback.
-
D.
audioChannelsType
Indicates the type or configuration of audio channels used in an audio signal or recording (e.g., mono, stereo, surround).
-
E.
polyphonicChannels
Indicates that an entity supports or involves multiple independent audio or musical channels that can sound simultaneously (polyphony).
- 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_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:58 a.m.