Triple
T14423502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khronos Group |
E357639
|
entity |
| Predicate | standard |
P1587
|
FINISHED |
| Object | OpenXR |
E1044588
|
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: OpenXR | Statement: [Khronos Group, standard, OpenXR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenXR Context triple: [Khronos Group, standard, OpenXR]
-
A.
OpenXR
chosen
OpenXR is an open, royalty-free standard that provides a unified API for developing virtual reality (VR) and augmented reality (AR) applications across diverse hardware and platforms.
-
B.
Oculus SDK
Oculus SDK is a software development kit that provides tools and APIs for creating virtual reality applications and experiences for Oculus headsets.
-
C.
Oculus runtime
Oculus runtime is the core software layer that manages VR hardware interaction, tracking, and application execution for Oculus virtual reality systems.
-
D.
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.
-
E.
SteamVR
SteamVR is Valve's virtual reality platform and software framework that enables VR gaming and experiences on PC through Steam.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91123f848190ba3fb18a76c2d24c |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bcd2a908190ad7d5ebf11b41551 |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.