Triple

T23259014
Position Surface form Disambiguated ID Type / Status
Subject wasi-filesystem E581952 entity
Predicate relatedTo P37 FINISHED
Object wasi-cli NE NERFINISHED

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: wasi-cli | Statement: [wasi-filesystem, relatedTo, wasi-cli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: wasi-cli
Context triple: [wasi-filesystem, relatedTo, wasi-cli]
  • A. wasi-cli chosen
    wasi-cli is a command-line interface component for the WebAssembly System Interface (WASI) that enables running and interacting with WASI-compatible WebAssembly modules from the terminal.
  • B. wasi-filesystem
    wasi-filesystem is a WebAssembly System Interface (WASI) proposal and library that defines standardized APIs for interacting with files and directories in a sandboxed, platform-independent way.
  • C. Wasmtime
    Wasmtime is a fast, secure, and embeddable WebAssembly runtime designed for running WebAssembly modules outside the browser in various applications and services.
  • D. wasi-http
    wasi-http is a WebAssembly System Interface (WASI) proposal that defines standardized APIs for performing HTTP operations from WebAssembly modules in a secure, host-agnostic way.
  • E. wasi-io
    wasi-io is a WebAssembly System Interface (WASI) component that defines standardized I/O APIs for handling streams, files, and related input/output operations in WebAssembly environments.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e246079f58819085eaa9c260906880 completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f194c710c48190aff03d210642a043 completed April 29, 2026, 5:19 a.m.
Created at: April 17, 2026, 4:11 p.m.