Triple
T20192985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niantic |
E493017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | augmented reality company |
C27198
|
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: augmented reality company Context triple: [Niantic, instanceOf, augmented reality company]
-
A.
virtual reality production company
A virtual reality production company is a creative and technical studio that designs, develops, and delivers immersive VR experiences, content, and applications for entertainment, training, marketing, and other interactive uses.
-
B.
simulation technology company
A simulation technology company develops advanced software and hardware systems that create realistic virtual models of real-world processes, environments, or products to support training, analysis, design, and decision-making.
-
C.
location-based services company
chosen
A location-based services company provides digital products or platforms that use geographic data and real-time positioning to deliver context-aware information, navigation, and analytics to businesses or consumers.
-
D.
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.
-
E.
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.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.