Triple
T6443470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wasi-cli |
E138281
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | wasmer |
E138283
|
NE FINISHED |
How this triple was built (2 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: wasmer | Statement: [wasi-cli, relatedTo, wasmer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: wasmer Context triple: [wasi-cli, relatedTo, wasmer]
-
A.
Wasmtime
Wasmtime is a fast, secure, and embeddable WebAssembly runtime designed for running WebAssembly modules outside the browser in various applications and services.
-
B.
WasmEdge
WasmEdge is a high-performance, lightweight WebAssembly runtime optimized for cloud-native, edge, and serverless applications.
-
C.
WebAssembly System Interface
The WebAssembly System Interface (WASI) is a modular, portable set of system APIs that allows WebAssembly programs to interact safely and consistently with operating system features like files, networking, and clocks across different platforms.
-
D.
Wasmer runtime
chosen
Wasmer runtime is a high-performance, cross-platform WebAssembly runtime that enables running WebAssembly modules on servers, desktops, and embedded systems.
-
E.
WASI component model
The WASI component model is a modular framework for composing, linking, and running WebAssembly components with well-defined interfaces and capability-based security across different hosts and languages.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c65fc86d0c8190a254126255a7af1b |
completed | March 27, 2026, 10:45 a.m. |
Created at: March 22, 2026, 4:46 p.m.