Triple
T29182023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149 |
E739767
|
entity |
| Predicate | isUsedForChiptuneMusic |
P168649
|
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, isUsedForChiptuneMusic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedForChiptuneMusic Context triple: [Yamaha YM2149, isUsedForChiptuneMusic, true]
-
A.
soundChip
Indicates that one entity functions as or contains the sound-processing chip used by another entity.
-
B.
isUsedToPlay
Indicates that something serves as an instrument, tool, or medium for engaging in a game, sport, or other form of play.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
supportsNoiseChannel
Indicates that one entity is capable of handling, transmitting, or operating with a specified noise channel in a system or process.
-
E.
musicUsed
Indicates that one entity makes use of or incorporates another entity as music, such as in a performance, production, or media context.
- 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_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 28, 2026, 11:58 a.m.