Triple
T32173545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XpanD 3D |
E821773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 3D technology provider |
C2666
|
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: 3D technology provider Context triple: [XpanD 3D, instanceOf, 3D technology provider]
-
A.
cinema technology brand
chosen
A cinema technology brand is a company that designs, manufactures, and markets specialized audio-visual systems, projection equipment, and related technologies to enhance the movie theater viewing experience.
-
B.
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.
-
C.
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.
-
D.
surround sound technology developer
A surround sound technology developer designs, engineers, and optimizes multi-channel audio systems and algorithms to create immersive, spatial listening experiences across various media and devices.
-
E.
graphics hardware company
A graphics hardware company is an organization that designs, manufactures, and markets specialized processing units and related components to accelerate rendering, visualization, and computation for computers and electronic 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:33 a.m.