Triple
T12480375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huawei Mobile Services |
E298287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile service ecosystem |
C16816
|
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: mobile service ecosystem Context triple: [Huawei Mobile Services, instanceOf, mobile service ecosystem]
-
A.
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.
-
B.
software and services ecosystem
chosen
A software and services ecosystem is an interconnected network of applications, platforms, tools, and providers that collaboratively deliver integrated digital capabilities and value to users and organizations.
-
C.
mobile satellite service system
A mobile satellite service system is a communication network that uses satellites to provide voice, data, and messaging connectivity to mobile users over wide geographic areas, including remote and underserved regions.
-
D.
universal service support mechanism
A universal service support mechanism is a regulatory and financial framework designed to ensure that essential communication services are available, affordable, and accessible to all users, including those in high-cost or underserved areas.
-
E.
public service system
A public service system is an organized framework of institutions, processes, and resources designed to deliver essential services and support to the public in an efficient, equitable, and transparent manner.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.