Triple
T22062724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPF |
E545191
|
entity |
| Predicate | supportsFeature |
P203
|
FINISHED |
| Object | Uplink Classifier |
—
|
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: Uplink Classifier | Statement: [UPF, supportsFeature, Uplink Classifier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uplink Classifier Context triple: [UPF, supportsFeature, Uplink Classifier]
-
A.
Long Term Evolution for Machines
Long Term Evolution for Machines is a low-power wide-area cellular technology based on LTE, designed to provide efficient, secure, and cost-effective connectivity for Internet of Things (IoT) devices.
-
B.
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.
-
C.
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.
-
D.
3GPP TS 36.211
3GPP TS 36.211 is a technical specification that defines the physical layer procedures and signal structures for LTE (E-UTRA) radio access in mobile communication systems.
-
E.
IEEE 802.1CM fronthaul standard
The IEEE 802.1CM fronthaul standard is a Time-Sensitive Networking (TSN) specification that defines Ethernet-based transport requirements and profiles for carrying mobile fronthaul traffic in 4G/5G radio access 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: Uplink Classifier Target entity description: Uplink Classifier is a 5G core network function component that classifies and steers uplink user traffic based on defined policies and QoS rules.
-
A.
Long Term Evolution for Machines
Long Term Evolution for Machines is a low-power wide-area cellular technology based on LTE, designed to provide efficient, secure, and cost-effective connectivity for Internet of Things (IoT) devices.
-
B.
5G User Plane Function (UPF)
chosen
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.
-
C.
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.
-
D.
3GPP TS 36.211
3GPP TS 36.211 is a technical specification that defines the physical layer procedures and signal structures for LTE (E-UTRA) radio access in mobile communication systems.
-
E.
IEEE 802.1CM fronthaul standard
The IEEE 802.1CM fronthaul standard is a Time-Sensitive Networking (TSN) specification that defines Ethernet-based transport requirements and profiles for carrying mobile fronthaul traffic in 4G/5G radio access networks.
- F. None of above.
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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285e8c688190b701e417893cc148 |
completed | April 28, 2026, 9:36 p.m. |
Created at: April 16, 2026, 8:27 p.m.