Triple
T23302245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rel-16 |
E590334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 5G NR release |
C46815
|
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: 5G NR release Context triple: [Rel-16, instanceOf, 5G NR release]
-
A.
5G NR specification family
chosen
The 5G NR specification family is a comprehensive set of 3GPP standards that define the radio interface, protocols, and features enabling fifth-generation mobile networks for enhanced mobile broadband, ultra-reliable low-latency communication, and massive machine-type connectivity.
-
B.
5G System specification
A 5G System specification defines the technical requirements, architecture, interfaces, and operational procedures that govern the design, deployment, and interoperability of fifth-generation mobile communication networks.
-
C.
5G NAS specification
The 5G NAS specification defines the signaling procedures, message formats, and protocols used between user equipment and the 5G core network for functions such as registration, session management, mobility, and security at the non-access stratum layer.
-
D.
5G NAS protocol specification
The 5G NAS protocol specification defines the signaling procedures, message formats, and state machines used between user equipment and the 5G core network for mobility management, session management, and security at the non-access stratum layer.
-
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.
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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:04 p.m.