Triple
T30025689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS VR Processor Unit |
E762874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | virtual reality headset accessory |
C56652
|
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: virtual reality headset accessory Context triple: [PS VR Processor Unit, instanceOf, virtual reality headset accessory]
-
A.
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.
-
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.
virtual reality hardware manufacturer
A virtual reality hardware manufacturer is a company that designs, produces, and distributes physical devices such as headsets, controllers, sensors, and related equipment that enable immersive VR experiences.
-
D.
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.
-
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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:48 p.m.