Triple
T29182020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149 |
E739767
|
entity |
| Predicate | hasNoiseFrequencyControl |
P200365
|
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, hasNoiseFrequencyControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoiseFrequencyControl Context triple: [Yamaha YM2149, hasNoiseFrequencyControl, true]
-
A.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
-
B.
supportsNoiseChannel
Indicates that one entity is capable of handling, transmitting, or operating with a specified noise channel in a system or process.
-
C.
hasNoisePerformance
Indicates the degree to which one entity’s operation or behavior produces or is characterized by a certain level or quality of noise.
-
D.
hasNoiseGenerator
Indicates that an entity is equipped with or associated with a device or mechanism that produces noise.
-
E.
hasNoiseTerm
Indicates that a given expression, model, or equation includes an additional noise term representing random or unexplained variation.
- 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_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
| PDg | Predicate description generation | batch_69ff84dec2848190b67a497d025c8880 |
completed | May 9, 2026, 7:02 p.m. |
Created at: April 28, 2026, 11:58 a.m.