Triple
T22062235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSUPA |
E545181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile telecommunication protocol |
C44328
|
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 telecommunication protocol Context triple: [HSUPA, instanceOf, mobile telecommunication protocol]
-
A.
mobile core network protocol
A mobile core network protocol is a set of standardized rules and procedures that govern how data, signaling, and control information are exchanged within the core of a mobile communication network to enable connectivity, mobility, and services for users.
-
B.
telecommunications standard
A telecommunications standard is an agreed-upon set of technical specifications and protocols that ensure compatibility, interoperability, and reliable communication across different telecom networks and devices.
-
C.
E-UTRAN protocol layer
chosen
The E-UTRAN protocol layer is the set of radio interface protocols in LTE that manage user data transfer, control signaling, and radio resource handling between the user equipment and the evolved NodeB.
-
D.
communication protocol suite
A communication protocol suite is a coordinated set of network protocols that work together across different layers to enable reliable data exchange between devices in a communication system.
-
E.
IMT-2000 radio interface
An IMT-2000 radio interface is a standardized third-generation (3G) mobile communication air interface specification that defines how user equipment and networks exchange radio signals to provide global, interoperable wireless voice and data services.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:27 p.m.