WASI
E138279
WASI is a modular system interface designed to let WebAssembly programs safely and portably interact with operating system features like files, networking, and clocks.
All labels observed (4)
| Label | Occurrences |
|---|---|
| WASI canonical | 9 |
| WASI (WebAssembly System Interface) | 1 |
| WASI CG | 1 |
| WASI Preview 2 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1210045 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WASI Context triple: [WebAssembly System Interface, abbreviation, WASI]
-
A.
WAS
WAS is the standard three-letter abbreviation used for the Washington Commanders NFL franchise.
-
B.
WAS
WAS is the station code for Washington, D.C.’s main intercity and commuter rail hub, Union Station.
-
C.
WAS
WAS is the standard three-letter abbreviation used for the NBA team Washington Wizards.
-
D.
WES
WES is a commuter rail service in the Portland, Oregon metropolitan area that connects Beaverton and Wilsonville.
-
E.
WAI
WAI (Web Accessibility Initiative) is a World Wide Web Consortium (W3C) program that develops guidelines, resources, and standards to make the web accessible to people with disabilities.
- 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: WASI Target entity description: WASI is a modular system interface designed to let WebAssembly programs safely and portably interact with operating system features like files, networking, and clocks.
-
A.
WAS
WAS is the standard three-letter abbreviation used for the Washington Commanders NFL franchise.
-
B.
WAS
WAS is the station code for Washington, D.C.’s main intercity and commuter rail hub, Union Station.
-
C.
WAS
WAS is the standard three-letter abbreviation used for the NBA team Washington Wizards.
-
D.
WES
WES is a commuter rail service in the Portland, Oregon metropolitan area that connects Beaverton and Wilsonville.
-
E.
WAI
WAI (Web Accessibility Initiative) is a World Wide Web Consortium (W3C) program that develops guidelines, resources, and standards to make the web accessible to people with disabilities.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
WebAssembly standard
ⓘ
system interface specification ⓘ |
| abbreviationOf | WebAssembly System Interface ⓘ |
| compatibleWith |
Linux
ⓘ
Windows ⓘ embedded and edge environments ⓘ macOS ⓘ |
| designedFor |
WebAssembly
ⓘ
linked to:
WebAssembly specification
|
| designPrinciple |
capability-based security model
ⓘ
host-agnostic abstractions ⓘ modular APIs grouped into separate proposals ⓘ |
| developedBy | Bytecode Alliance ⓘ |
| ecosystem |
WebAssembly
ⓘ
linked to:
WebAssembly specification
|
| enables |
language-agnostic binaries targeting multiple platforms
ⓘ
running WebAssembly outside web browsers ⓘ |
| fullName | WebAssembly System Interface ⓘ |
| goal |
deterministic behavior where possible
ⓘ
enable WebAssembly outside the browser ⓘ portability across operating systems ⓘ security through isolation ⓘ |
| hasComponent |
WASI Preview1
ⓘ
linked to:
WASI component model
WASI Preview2 ⓘ
linked to:
WASI component model
wasi-cli ⓘ wasi-clocks ⓘ wasi-filesystem ⓘ wasi-http ⓘ wasi-io ⓘ wasi-poll ⓘ wasi-random ⓘ wasi-sockets ⓘ |
| property |
capability-based
ⓘ
modular ⓘ sandbox-friendly ⓘ |
| purpose | to let WebAssembly programs interact with system resources safely and portably ⓘ |
| relatedTo |
WebAssembly core specification
ⓘ
linked to:
WebAssembly specification
component model for WebAssembly ⓘ |
| securityModel | capability-based handles instead of global namespaces ⓘ |
| standardizedBy |
W3C WebAssembly Community Group
ⓘ
linked to:
W3C Community Group
|
| supports |
clocks
ⓘ
environment variables ⓘ file system access ⓘ networking ⓘ process-like abstractions ⓘ randomness ⓘ standard error ⓘ standard input ⓘ standard output ⓘ |
| usedIn |
container-like sandboxing
ⓘ
edge computing platforms ⓘ plugin systems ⓘ server-side WebAssembly runtimes ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: WASI Description of subject: WASI is a modular system interface designed to let WebAssembly programs safely and portably interact with operating system features like files, networking, and clocks.
Referenced by (12)
Full triples — surface form annotated when it differs from this entity's canonical label.