Triple
T21269717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serving GPRS Support Node |
E524221
|
entity |
| Predicate | replacedBy |
P101
|
FINISHED |
| Object | Serving Gateway in LTE |
—
|
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: Serving Gateway in LTE | Statement: [Serving GPRS Support Node, replacedBy, Serving Gateway in LTE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Serving Gateway in LTE Context triple: [Serving GPRS Support Node, replacedBy, Serving Gateway in LTE]
-
A.
Home eNodeB Gateway
A Home eNodeB Gateway is a core network element in LTE that aggregates and manages traffic and signaling from multiple residential or enterprise femtocell base stations (Home eNodeBs) to the operator’s core network.
-
B.
Serving GPRS Support Node
The Serving GPRS Support Node (SGSN) is a core network component in 2G/3G mobile systems responsible for delivering data packets to and from mobile devices and managing their mobility and session states.
-
C.
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.
-
D.
Access and Mobility Management Function
The Access and Mobility Management Function (AMF) is a key 5G core network control-plane function responsible for user equipment registration, connection and mobility management, and access authentication.
-
E.
Gateway Mobile Switching Centre
The Gateway Mobile Switching Centre (GMSC) is a key GSM network component that routes calls between mobile networks and external networks such as the public switched telephone network (PSTN).
- 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: Serving Gateway in LTE Target entity description: The Serving Gateway in LTE is a core network element that routes and forwards user data packets, anchors user sessions during mobility, and interfaces between the radio access network and the packet data network.
-
A.
Home eNodeB Gateway
A Home eNodeB Gateway is a core network element in LTE that aggregates and manages traffic and signaling from multiple residential or enterprise femtocell base stations (Home eNodeBs) to the operator’s core network.
-
B.
Serving GPRS Support Node
The Serving GPRS Support Node (SGSN) is a core network component in 2G/3G mobile systems responsible for delivering data packets to and from mobile devices and managing their mobility and session states.
-
C.
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.
-
D.
Access and Mobility Management Function
The Access and Mobility Management Function (AMF) is a key 5G core network control-plane function responsible for user equipment registration, connection and mobility management, and access authentication.
-
E.
Gateway Mobile Switching Centre
The Gateway Mobile Switching Centre (GMSC) is a key GSM network component that routes calls between mobile networks and external networks such as the public switched telephone network (PSTN).
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651c9208190a87d45acd6fafaaa |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:01 p.m.