Triple
T27629718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlackBerry UEM |
E696304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | enterprise mobility management platform |
C29597
|
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: enterprise mobility management platform Context triple: [BlackBerry UEM, instanceOf, enterprise mobility management platform]
-
A.
enterprise software-as-a-service platform
An enterprise software-as-a-service platform is a cloud-based solution that delivers scalable, secure, and centrally managed business applications to organizations on a subscription basis.
-
B.
device management portal
chosen
A device management portal is a centralized web-based interface that allows administrators to monitor, configure, secure, and maintain a fleet of devices throughout their lifecycle.
-
C.
enterprise portal software
Enterprise portal software is a centralized, web-based platform that integrates applications, data, and services to provide personalized, secure access and collaboration tools for employees, partners, and customers across an organization.
-
D.
application lifecycle management platform
An application lifecycle management platform is an integrated system that supports planning, development, testing, deployment, maintenance, and governance of software applications throughout their entire lifecycle.
-
E.
mobile security service
A mobile security service is a system that protects mobile devices, applications, and data from threats through features like malware detection, secure communication, access control, and real-time monitoring.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:20 p.m.