Triple
T23042192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TS 44-series |
E573766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GSM/EDGE radio interface specification |
C44329
|
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: GSM/EDGE radio interface specification Context triple: [TS 44-series, instanceOf, GSM/EDGE radio interface specification]
-
A.
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.
-
B.
E-UTRAN protocol layer
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.
-
C.
3G radio access network
A 3G radio access network is the part of a mobile communication system that uses third-generation wireless technology to connect user devices to the core network via radio base stations and related control equipment.
-
D.
2G radio access network
chosen
A 2G radio access network is the collection of base stations, controllers, and related interfaces that provide digital cellular connectivity between mobile devices and the core network using second-generation (2G) wireless technologies such as GSM.
-
E.
3GPP network node
A 3GPP network node is a standardized functional entity within a 3GPP-defined mobile network (such as LTE or 5G) that performs specific control, user-plane, or management tasks to enable communication 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:54 p.m.