Triple
T29035561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2203 |
E737848
|
entity |
| Predicate | hasFMOperatorsPerChannel |
P82802
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Yamaha YM2203, hasFMOperatorsPerChannel, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFMOperatorsPerChannel Context triple: [Yamaha YM2203, hasFMOperatorsPerChannel, 4]
-
A.
hasNumberOfFMChannels
Indicates the relationship that specifies how many FM (frequency modulation) channels are associated with or supported by an entity.
-
B.
hasFrequencyChannels
Indicates that an entity is associated with, or operates over, one or more specific frequency channels.
-
C.
hasOperatorPerChannelCount
chosen
Indicates that each channel in a system or context is associated with a specific number of operators assigned to it.
-
D.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
E.
hasFullBandwidthChannels
Indicates that the subject possesses communication channels that operate at the maximum or designated full data transmission capacity.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603c9e4081908129011e8294db5a |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:58 a.m.