Triple
T28613175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Data rates for GSM Evolution |
E724216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 2.5G technology |
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: 2.5G technology Context triple: [Enhanced Data rates for GSM Evolution, instanceOf, 2.5G technology]
-
A.
IMT-2000 family member
An IMT-2000 family member is a mobile communication system that conforms to the ITU’s IMT-2000 (3G) standards, ensuring global interoperability, high-speed data, and advanced multimedia services.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
200 Gigabit Ethernet technology
200 Gigabit Ethernet technology is a high-speed networking standard that delivers 200 gigabits per second of data throughput, enabling faster data center, enterprise, and carrier network performance.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:31 a.m.