Triple
T22489262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Audio API |
E555970
|
entity |
| Predicate | coreConcept |
P533
|
FINISHED |
| Object | MediaStreamAudioDestinationNode |
—
|
NE NERFINISHED |
How this triple was built (3 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: MediaStreamAudioDestinationNode | Statement: [Web Audio API, coreConcept, MediaStreamAudioDestinationNode]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MediaStreamAudioDestinationNode Context triple: [Web Audio API, coreConcept, MediaStreamAudioDestinationNode]
-
A.
MediaStreamAudioSourceNode
MediaStreamAudioSourceNode is a Web Audio API interface that represents an audio source whose input comes from a MediaStream, such as a user’s microphone or camera.
-
B.
MediaElementAudioSourceNode
MediaElementAudioSourceNode is a Web Audio API interface that lets you use the audio output of an HTML media element (like `<audio>` or `<video>`) as a source node in an audio processing graph.
-
C.
AudioNode
AudioNode is a fundamental building block in the Web Audio API that represents an audio processing module which can be connected to other nodes to create complex audio graphs in web applications.
-
D.
MediaStreamTrack
MediaStreamTrack is a WebRTC API interface representing a single media source stream, such as an audio or video track, that can be transmitted, processed, or combined in real-time communications.
-
E.
Web Audio API
The Web Audio API is a high-level JavaScript API for creating, processing, and controlling audio in web applications, enabling complex audio effects, spatialization, and real-time audio synthesis directly in the browser.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MediaStreamAudioDestinationNode Target entity description: MediaStreamAudioDestinationNode is a Web Audio API interface that routes audio from an audio graph into a MediaStream, enabling capture, recording, or transmission of the processed sound.
-
A.
MediaStreamAudioSourceNode
MediaStreamAudioSourceNode is a Web Audio API interface that represents an audio source whose input comes from a MediaStream, such as a user’s microphone or camera.
-
B.
MediaElementAudioSourceNode
MediaElementAudioSourceNode is a Web Audio API interface that lets you use the audio output of an HTML media element (like `<audio>` or `<video>`) as a source node in an audio processing graph.
-
C.
AudioNode
AudioNode is a fundamental building block in the Web Audio API that represents an audio processing module which can be connected to other nodes to create complex audio graphs in web applications.
-
D.
MediaStreamTrack
MediaStreamTrack is a WebRTC API interface representing a single media source stream, such as an audio or video track, that can be transmitted, processed, or combined in real-time communications.
-
E.
Web Audio API
The Web Audio API is a high-level JavaScript API for creating, processing, and controlling audio in web applications, enabling complex audio effects, spatialization, and real-time audio synthesis directly in the browser.
- F. None of above. chosen
Provenance (2 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3f3b4c819092bfe6495c61db46 |
completed | April 29, 2026, 1:17 a.m. |
Created at: April 16, 2026, 8:49 p.m.