Triple
T29606547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electric Communities |
E754590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | virtual worlds company |
C55960
|
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 worlds company Context triple: [Electric Communities, instanceOf, virtual worlds 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.
virtual organization
A virtual organization is a flexible, often temporary network of geographically dispersed individuals, teams, or organizations that collaborate primarily through digital communication technologies to achieve shared goals without a traditional centralized physical structure.
-
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.
virtualization company
A virtualization company provides software and platforms that abstract and simulate computing resources—such as servers, storage, networks, or desktops—to enable more efficient, flexible, and scalable IT infrastructure.
-
E.
virtual reality studio
A virtual reality studio is a specialized environment equipped with hardware, software, and creative tools for designing, developing, and producing immersive VR experiences and content.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:25 p.m.