Triple
T9027692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EyeSight external display |
E216088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mixed reality headset feature |
C25486
|
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 feature Context triple: [EyeSight external display, instanceOf, mixed reality headset feature]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
HDMI feature
An HDMI feature is a specific capability or enhancement supported by an HDMI interface—such as audio return, Ethernet over HDMI, or high dynamic range—that defines how audio, video, and data are transmitted and experienced between connected devices.
-
E.
mobile operating system feature
A mobile operating system feature is a built-in software capability or service within a smartphone or tablet OS that enhances device functionality, user interaction, performance, or security.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:07 p.m.