Triple
T24027263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wasi-clocks |
E594999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | WebAssembly interface |
C6414
|
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 interface Context triple: [wasi-clocks, instanceOf, WebAssembly interface]
-
A.
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.
-
B.
WebAssembly API method
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.
-
C.
WebAssembly-related standard
chosen
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 interface
A WebRTC interface is a conceptual class that encapsulates the APIs and logic required to establish, manage, and terminate real-time audio, video, and data communication between peers directly in web applications.
-
E.
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.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:54 p.m.