Triple
T29182018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149 |
E739767
|
entity |
| Predicate | supportsSoftwareControl |
P204038
|
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, supportsSoftwareControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSoftwareControl Context triple: [Yamaha YM2149, supportsSoftwareControl, true]
-
A.
supportsCommandAndControl
Indicates that an entity enables, facilitates, or maintains command-and-control functions for another entity or operation.
-
B.
supportsImmediateControl
Indicates that one entity enables or allows another entity to exercise direct, real-time control over it without intermediate steps or delays.
-
C.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
-
D.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
E.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a031045669c8190944781a48d09b5b6 |
completed | May 12, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_6a030fa775848190839b388f950d0364 |
completed | May 12, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_6a031044b88481909092553ee4198fd5 |
completed | May 12, 2026, 11:34 a.m. |
Created at: April 28, 2026, 11:58 a.m.