Triple

T22041227
Position Surface form Disambiguated ID Type / Status
Subject WebAssembly.Module E544640 entity
Predicate operatesOn P23 FINISHED
Object WebAssembly binary format (.wasm) — 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: WebAssembly binary format (.wasm) | Statement: [WebAssembly.Module, operatesOn, WebAssembly binary format (.wasm)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: WebAssembly binary format (.wasm)
Context triple: [WebAssembly.Module, operatesOn, WebAssembly binary format (.wasm)]
  • A. 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.
  • B. WebAssembly.Module
    WebAssembly.Module is a JavaScript object representing a compiled WebAssembly binary that can be efficiently instantiated and executed in web or other host environments.
  • 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. Wasmtime
    Wasmtime is a fast, secure, and embeddable WebAssembly runtime designed for running WebAssembly modules outside the browser in various applications and services.
  • E. 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.
  • 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: WebAssembly binary format (.wasm)
Target entity description: The WebAssembly binary format (.wasm) is a compact, platform-independent bytecode representation designed for efficient execution of code—often compiled from languages like C, C++, or Rust—inside web browsers and other runtimes.
  • A. WebAssembly specification chosen
    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.
  • B. WebAssembly.Module
    WebAssembly.Module is a JavaScript object representing a compiled WebAssembly binary that can be efficiently instantiated and executed in web or other host environments.
  • 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. Wasmtime
    Wasmtime is a fast, secure, and embeddable WebAssembly runtime designed for running WebAssembly modules outside the browser in various applications and services.
  • E. 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.
  • F. None of above.

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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12828fc788190a22c0e9c2372656b completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:25 p.m.