Triple
T22062699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPF |
E545191
|
entity |
| Predicate | definedInSpecification |
P5374
|
FINISHED |
| Object | 3GPP TS 29.244 |
—
|
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: 3GPP TS 29.244 | Statement: [UPF, definedInSpecification, 3GPP TS 29.244]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 29.244 Context triple: [UPF, definedInSpecification, 3GPP TS 29.244]
-
A.
3GPP TS 29.214
3GPP TS 29.214 is a 3rd Generation Partnership Project technical specification that defines the policy and charging control signaling procedures and interfaces between core network elements in mobile communication systems.
-
B.
3GPP TS 29.274
3GPP TS 29.274 is a technical specification that defines the GPRS Tunnelling Protocol (GTPv2-C) for control plane signaling between core network nodes in 4G LTE and related mobile networks.
-
C.
3GPP TS 24.229
3GPP TS 24.229 is a core 3GPP specification that defines the signaling procedures and call control for IP Multimedia Subsystem (IMS) services over SIP in mobile and fixed networks.
-
D.
3GPP TS 26.441
3GPP TS 26.441 is a 3rd Generation Partnership Project technical specification that defines the detailed codec description and implementation guidelines for the Enhanced Voice Services (EVS) audio codec used in modern mobile communication systems.
-
E.
3GPP TS 26.444
3GPP TS 26.444 is a 3GPP technical specification that defines the Enhanced Voice Services (EVS) codec for high-quality, efficient voice communication over mobile 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: 3GPP TS 29.244 Target entity description: 3GPP TS 29.244 is a 3GPP technical specification that defines the control and user plane separation (CUPS) and related interfaces for the 5G core user plane function (UPF) in mobile networks.
-
A.
3GPP TS 29.214
3GPP TS 29.214 is a 3rd Generation Partnership Project technical specification that defines the policy and charging control signaling procedures and interfaces between core network elements in mobile communication systems.
-
B.
3GPP TS 29.274
3GPP TS 29.274 is a technical specification that defines the GPRS Tunnelling Protocol (GTPv2-C) for control plane signaling between core network nodes in 4G LTE and related mobile networks.
-
C.
3GPP TS 24.229
3GPP TS 24.229 is a core 3GPP specification that defines the signaling procedures and call control for IP Multimedia Subsystem (IMS) services over SIP in mobile and fixed networks.
-
D.
3GPP TS 26.441
3GPP TS 26.441 is a 3rd Generation Partnership Project technical specification that defines the detailed codec description and implementation guidelines for the Enhanced Voice Services (EVS) audio codec used in modern mobile communication systems.
-
E.
3GPP TS 26.444
3GPP TS 26.444 is a 3GPP technical specification that defines the Enhanced Voice Services (EVS) codec for high-quality, efficient voice communication over mobile 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_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.