Triple
T1103199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly JavaScript Interface |
E25427
|
entity |
| Predicate | standardizedBy |
P1371
|
FINISHED |
| Object | W3C WebAssembly Working Group |
E20599
|
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: W3C WebAssembly Working Group | Statement: [WebAssembly JavaScript Interface, standardizedBy, W3C WebAssembly Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: W3C WebAssembly Working Group Context triple: [WebAssembly JavaScript Interface, standardizedBy, W3C WebAssembly Working Group]
-
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 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.
-
C.
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.
-
D.
W3C Working Group
chosen
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
-
E.
WHATWG
WHATWG is a community-driven standards organization that develops and maintains key web technologies, including the living standard for HTML.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c375848190baec4d534f489616 |
completed | March 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac4c47dbf88190a1898d7bda32ecb2 |
completed | March 7, 2026, 4:03 p.m. |
Created at: March 1, 2026, 7:43 p.m.