Triple
T24027665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WASI Community Group |
E595010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | WebAssembly-related organization |
C13213
|
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-related organization Context triple: [WASI Community Group, instanceOf, WebAssembly-related organization]
-
A.
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.
-
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 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.
-
D.
blockchain organization
A blockchain organization is an entity that coordinates people, resources, and processes using blockchain-based infrastructure—often including smart contracts and decentralized governance—to manage operations, assets, and decision-making in a transparent and tamper-resistant manner.
-
E.
open-source organization
chosen
An open-source organization is a collaborative entity that develops, maintains, and governs software or other projects whose source materials are publicly accessible, modifiable, and distributable under open licenses.
- 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.