Triple

T17234339
Position Surface form Disambiguated ID Type / Status
Subject Chrome Web Platform features E418320 entity
Predicate includesAPI P126488 FINISHED
Object WebGPU E357641 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: WebGPU | Statement: [Chrome Web Platform features, includesAPI, WebGPU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WebGPU
Context triple: [Chrome Web Platform features, includesAPI, WebGPU]
  • A. WebGPU chosen
    WebGPU is a modern web graphics and compute API designed to provide high-performance, low-level access to GPU capabilities in browsers, succeeding and improving upon WebGL.
  • B. WebGPU Shading Language
    WebGPU Shading Language is a modern, strongly typed shading language designed specifically for the WebGPU API to write portable, high-performance GPU shaders for web applications.
  • C. WebGL
    WebGL is a JavaScript API that enables hardware-accelerated 2D and 3D graphics rendering within web browsers without the need for plugins.
  • D. Vulkan
    Vulkan is a low-overhead, cross-platform 3D graphics and compute API designed to provide high-performance access to modern GPUs.
  • E. WebVR / WebXR APIs
    WebVR / WebXR APIs are web standards that enable immersive virtual and augmented reality experiences directly in the browser without requiring native applications.
  • 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_69d886d8e96081909870bff6c3d0bf09 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42dfa0a408190880804d463305867 completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01676382388190ab82bd10bd53f59e completed May 11, 2026, 5:21 a.m.
Created at: April 10, 2026, 5:39 a.m.