Triple
T15838179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSNG |
E384035
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile uplink system |
C27745
|
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 uplink system Context triple: [DSNG, instanceOf, mobile uplink system]
-
A.
mobile satellite service system
chosen
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.
-
B.
mobile portal operator
A mobile portal operator is an entity that manages and delivers curated content, services, and applications to users through a centralized interface on mobile devices, often integrating billing, access control, and partnerships with content providers.
-
C.
mobile phone line
A mobile phone line is a telecommunications service subscription that assigns a unique phone number and network access to a mobile device for voice, text, and data communication.
-
D.
wireless communication device
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
E.
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.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.