Triple
T23676348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NG-RAN |
E584887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Radio access network architecture |
C47942
|
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: Radio access network architecture Context triple: [NG-RAN, instanceOf, Radio access network architecture]
-
A.
radio access technology standard
A radio access technology standard is a defined set of technical specifications that governs how wireless devices connect to and communicate over a radio-based network interface.
-
B.
radio access technology feature
A radio access technology feature is a specific capability or enhancement within a wireless communication system’s radio interface that improves performance, efficiency, coverage, or user experience.
-
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
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.
5G NR radio access node
A 5G NR radio access node is a network element that implements the 5G New Radio air interface to connect user equipment to the core network, handling radio transmission, reception, and related control functions.
- F. None of above. chosen
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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:51 p.m.