Triple
T29101436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YMF276 |
E736647
|
entity |
| Predicate | audioApplication |
P167398
|
FINISHED |
| Object | game audio |
—
|
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: game audio | Statement: [Yamaha YMF276, audioApplication, game audio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioApplication Context triple: [Yamaha YMF276, audioApplication, game audio]
-
A.
audioStack
Indicates that one audio element is layered or queued on top of another within an ordered audio sequence or mix.
-
B.
audioStreaming
Indicates that one entity is transmitting audio data in real time for another entity to receive or play back.
-
C.
audioFocus
Indicates that one entity has priority or control over audio playback or attention relative to other potential audio sources.
-
D.
hearsApplications
Indicates that an entity (such as a person or body) formally receives and considers applications submitted by others.
-
E.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 11:12 a.m.