Triple
T29035562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2203 |
E737848
|
entity |
| Predicate | supportsFMAlgorithms |
P203941
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Yamaha YM2203, supportsFMAlgorithms, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFMAlgorithms Context triple: [Yamaha YM2203, supportsFMAlgorithms, 8]
-
A.
supportsOptimizationAlgorithm
Indicates that one entity is capable of running, integrating, or being compatible with a specified optimization algorithm.
-
B.
hasRankingAlgorithm
Indicates that an entity uses or is associated with a specific algorithm for ranking or ordering items.
-
C.
relatedAlgorithm
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
-
D.
includesAlgorithmFor
Indicates that one entity contains or incorporates a specific algorithm as part of its design, implementation, or functionality.
-
E.
algorithmFamily
Indicates that one algorithm belongs to, or is categorized under, a broader family or class of related algorithms.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02fc3890a881908b69b0f2d7cc1ce1 |
completed | May 12, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_6a02fb98438c8190938896c00216b9ec |
completed | May 12, 2026, 10:06 a.m. |
| PDg | Predicate description generation | batch_6a02fc379d1c8190aeb144f093169cfa |
completed | May 12, 2026, 10:08 a.m. |
Created at: April 28, 2026, 9:58 a.m.