Triple
T8602845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2151 |
E203720
|
entity |
| Predicate | hasSynthesisType |
P45518
|
FINISHED |
| Object | frequency modulation synthesis |
—
|
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: frequency modulation synthesis | Statement: [Yamaha YM2151, hasSynthesisType, frequency modulation synthesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSynthesisType Context triple: [Yamaha YM2151, hasSynthesisType, frequency modulation synthesis]
-
A.
synthesisType
chosen
Indicates the specific method, process, or pathway by which something is synthesized or produced.
-
B.
allowsSynthesisFromSources
Indicates that one entity permits the creation or production of something using specified source entities or materials.
-
C.
synthesizedAs
Indicates that one entity is produced or created in the form of another entity through a synthesis process.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasLanguageType
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46dc23448190a5eb63455578427e |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.