Triple
T22480075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 29.213 |
E555739
|
entity |
| Predicate | networkGeneration |
P67769
|
FINISHED |
| Object | 5G (interworking and EPC-based aspects) |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 5G (interworking and EPC-based aspects) | Statement: [3GPP TS 29.213, networkGeneration, 5G (interworking and EPC-based aspects)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 5G (interworking and EPC-based aspects) Context triple: [3GPP TS 29.213, networkGeneration, 5G (interworking and EPC-based aspects)]
-
A.
Network Functions in 5G Core
Network Functions in 5G Core are modular, service-based components—such as control, user plane, and management functions—that collaboratively deliver 5G connectivity, mobility, and service capabilities within the core network architecture.
-
B.
Evolved Packet Core
Evolved Packet Core is the 4G LTE mobile network architecture responsible for managing data connectivity, mobility, and services between user devices and external IP networks.
-
C.
3GPP TS 29.501
3GPP TS 29.501 is a technical specification that defines the system architecture and core network signaling interfaces for 5G networks within the 3GPP standards framework.
-
D.
3GPP TS 29.514
3GPP TS 29.514 is a 5G core network specification that defines the service-based interface and procedures for policy control between the Policy Control Function (PCF) and other network functions.
-
E.
5G User Plane Function (UPF)
The 5G User Plane Function (UPF) is a core network component in 5G architecture responsible for handling user data traffic, including packet routing, forwarding, and quality-of-service enforcement between user devices and data networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 5G (interworking and EPC-based aspects) Target entity description: 5G (interworking and EPC-based aspects) refers to the 3GPP-defined mechanisms and specifications that enable 5G networks to interoperate with and leverage the existing LTE/Evolved Packet Core infrastructure during the transition from 4G to full 5G deployment.
-
A.
Network Functions in 5G Core
Network Functions in 5G Core are modular, service-based components—such as control, user plane, and management functions—that collaboratively deliver 5G connectivity, mobility, and service capabilities within the core network architecture.
-
B.
Evolved Packet Core
Evolved Packet Core is the 4G LTE mobile network architecture responsible for managing data connectivity, mobility, and services between user devices and external IP networks.
-
C.
3GPP TS 29.501
3GPP TS 29.501 is a technical specification that defines the system architecture and core network signaling interfaces for 5G networks within the 3GPP standards framework.
-
D.
3GPP TS 29.514
3GPP TS 29.514 is a 5G core network specification that defines the service-based interface and procedures for policy control between the Policy Control Function (PCF) and other network functions.
-
E.
5G User Plane Function (UPF)
The 5G User Plane Function (UPF) is a core network component in 5G architecture responsible for handling user data traffic, including packet routing, forwarding, and quality-of-service enforcement between user devices and data networks.
- F. None of above. chosen
Provenance (2 batches)
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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3836a08190b6f0d88b94cb80a3 |
completed | April 29, 2026, 1:17 a.m. |
Created at: April 16, 2026, 8:49 p.m.