Triple
T22041192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly.Module |
E544640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | WebAssembly API interface |
C18795
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: WebAssembly API interface Context triple: [WebAssembly.Module, instanceOf, WebAssembly API interface]
-
A.
WebAssembly API method
chosen
A WebAssembly API method is a function exposed by the WebAssembly runtime or host environment that enables loading, instantiating, interacting with, and managing WebAssembly modules from external code.
-
B.
WebAssembly runtime
A WebAssembly runtime is a software environment that loads, validates, and executes WebAssembly modules, providing them with necessary system interfaces and resource management.
-
C.
WebAssembly-related standard
A WebAssembly-related standard is a formal specification that defines interoperable behaviors, formats, or APIs extending or integrating with the core WebAssembly platform to ensure consistent execution across diverse environments.
-
D.
WebRTC API interface
A WebRTC API interface is an abstraction layer that provides methods and events for establishing, managing, and controlling real-time audio, video, and data communication between peers directly in web applications.
-
E.
web API interface
A web API interface is a defined set of HTTP-based endpoints and data formats that allow external clients to programmatically interact with an application's functionality and resources.
- F. None of above.
Provenance (1 batch)
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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:25 p.m.