Triple
T8472807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2612 |
E200317
|
entity |
| Predicate | supportsPCM |
P82799
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yamaha YM2612, supportsPCM, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPCM Context triple: [Yamaha YM2612, supportsPCM, yes]
-
A.
supportsAudioQuality
Indicates that one entity provides or is compatible with a specified level or type of audio quality for another entity or context.
-
B.
supportedInstrument
Indicates that an entity provides compatibility with, or operational support for, a specified instrument.
-
C.
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.
-
D.
supportsInstrument
Indicates that one entity provides assistance, resources, or functionality that enables another entity (the instrument) to operate or be used effectively.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:11 p.m.