Triple
T7428123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasper Wireless |
E171418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | machine-to-machine communications company |
C424
|
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: machine-to-machine communications company Context triple: [Jasper Wireless, instanceOf, machine-to-machine communications company]
-
A.
telecommunications company
chosen
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
-
B.
telecommunications organization
A telecommunications organization is an entity that provides communication services and infrastructure—such as voice, data, and internet connectivity—across distances using wired, wireless, or satellite networks.
-
C.
Internet of Things platform
An Internet of Things platform is an integrated software and hardware environment that connects, manages, and analyzes data from distributed IoT devices to enable monitoring, control, and automation of physical systems.
-
D.
networking hardware company
A networking hardware company designs, manufactures, and sells physical devices and infrastructure that enable data communication and connectivity across computer networks.
-
E.
multinational technology conglomerate
A multinational technology conglomerate is a large corporation that operates across multiple countries and industries, owning and managing diverse technology-focused businesses under a unified corporate structure.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:12 p.m.