Triple

T23259106
Position Surface form Disambiguated ID Type / Status
Subject WASI component model E581954 entity
Predicate relatedTo P37 FINISHED
Object WIT (WebAssembly Interface Types) — NE NERFINISHED

How this triple was built (3 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: WIT (WebAssembly Interface Types) | Statement: [WASI component model, relatedTo, WIT (WebAssembly Interface Types)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: WIT (WebAssembly Interface Types)
Context triple: [WASI component model, relatedTo, WIT (WebAssembly Interface Types)]
  • A. 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.
  • B. WebAssembly JavaScript Interface
    The WebAssembly JavaScript Interface is the standard API that defines how JavaScript code interacts with and controls WebAssembly modules within web browsers and other host environments.
  • 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. WebAssembly specification
    The WebAssembly specification is a standardized, low-level binary instruction format designed to enable high-performance, portable code execution on the web and other platforms.
  • E. WebAssembly text format (wat)
    WebAssembly text format (wat) is a human-readable, textual representation of WebAssembly modules used for writing, inspecting, and debugging WebAssembly code.
  • 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: WIT (WebAssembly Interface Types)
Target entity description: WIT (WebAssembly Interface Types) is a language-agnostic interface definition format for WebAssembly that enables different modules and languages to interoperate cleanly within the component model.
  • A. 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.
  • B. WebAssembly JavaScript Interface
    The WebAssembly JavaScript Interface is the standard API that defines how JavaScript code interacts with and controls WebAssembly modules within web browsers and other host environments.
  • 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. WebAssembly specification
    The WebAssembly specification is a standardized, low-level binary instruction format designed to enable high-performance, portable code execution on the web and other platforms.
  • E. WebAssembly text format (wat)
    WebAssembly text format (wat) is a human-readable, textual representation of WebAssembly modules used for writing, inspecting, and debugging WebAssembly code.
  • F. None of above. chosen

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.