Triple
T22814535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Source Extensions |
E565064
|
entity |
| Predicate | apiSurface |
P149839
|
FINISHED |
| Object | MediaSource.addSourceBuffer() |
—
|
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: MediaSource.addSourceBuffer() | Statement: [Media Source Extensions, apiSurface, MediaSource.addSourceBuffer()]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MediaSource.addSourceBuffer() Context triple: [Media Source Extensions, apiSurface, MediaSource.addSourceBuffer()]
-
A.
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.
-
B.
HTMLMediaElement
HTMLMediaElement is a DOM interface in web browsers that represents media elements like audio and video, providing properties and methods to control their playback.
-
C.
AudioBufferSourceNode
AudioBufferSourceNode is a Web Audio API interface that plays audio from an in-memory buffer, often used as a primary source node for scheduling and controlling sound playback in web applications.
-
D.
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.
-
E.
Media Capture and Streams specification
The Media Capture and Streams specification is a W3C standard that defines how web applications can access and control audio and video streams from devices like cameras and microphones, enabling features such as getUserMedia in browsers.
- 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: MediaSource.addSourceBuffer() Target entity description: MediaSource.addSourceBuffer() is a JavaScript method that creates and returns a new SourceBuffer object for appending media segments to a MediaSource-backed HTMLMediaElement.
-
A.
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.
-
B.
HTMLMediaElement
HTMLMediaElement is a DOM interface in web browsers that represents media elements like audio and video, providing properties and methods to control their playback.
-
C.
AudioBufferSourceNode
AudioBufferSourceNode is a Web Audio API interface that plays audio from an in-memory buffer, often used as a primary source node for scheduling and controlling sound playback in web applications.
-
D.
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.
-
E.
Media Capture and Streams specification
The Media Capture and Streams specification is a W3C standard that defines how web applications can access and control audio and video streams from devices like cameras and microphones, enabling features such as getUserMedia in browsers.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
Created at: April 17, 2026, 3:33 p.m.