Triple
T27746438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Mixed Reality headsets |
E701996
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mixed reality headset family |
C53270
|
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: mixed reality headset family Context triple: [Windows Mixed Reality headsets, instanceOf, mixed reality headset family]
-
A.
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.
-
B.
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.
-
C.
virtual reality headset
A virtual reality headset is a wearable device that immerses the user in a computer-generated 3D environment by displaying stereoscopic images and tracking head movements.
-
D.
spatial computing platform
A spatial computing platform is an integrated hardware and software environment that blends digital content with the physical world, enabling users to interact with 3D information and experiences in real space.
-
E.
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.
- F. None of above. chosen
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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 4:16 p.m.