Triple
T33435038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebXR |
E856220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | extended reality web standard |
C59231
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: extended reality web standard Context triple: [WebXR, instanceOf, extended reality web standard]
-
A.
virtual reality web standard
chosen
A virtual reality web standard is a set of specifications and APIs that enable consistent creation, rendering, and interaction with immersive VR content directly within web browsers across different devices and platforms.
-
B.
mixed reality headset feature
A mixed reality headset feature is a specific capability or function that blends digital content with the physical environment to enhance user interaction, immersion, and situational awareness.
-
C.
mixed reality operating system
A mixed reality operating system is a software platform that seamlessly integrates and manages virtual and physical environments, enabling users to interact with digital content overlaid onto the real world through spatial computing interfaces and devices.
-
D.
virtual reality environment
A virtual reality environment is a computer-generated, immersive 3D space that users can interact with in real time through specialized hardware and software, simulating presence in a digital world.
-
E.
mixed reality headset family
A mixed reality headset family is a collection of related head-mounted devices that blend physical and digital environments, sharing a common platform, design language, and interaction paradigms while varying in capabilities, form factors, and target use cases.
- F. None of above.
Provenance (1 batch)
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.