Triple

T22480182
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 29.281 E555741 entity
Predicate usedBetween P17799 FINISHED
Object RNC and SGSN (Iu‑U interface) 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: RNC and SGSN (Iu‑U interface) | Statement: [3GPP TS 29.281, usedBetween, RNC and SGSN (Iu‑U interface)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RNC and SGSN (Iu‑U interface)
Context triple: [3GPP TS 29.281, usedBetween, RNC and SGSN (Iu‑U interface)]
  • A. Radio Network Controller (RNC)
    The Radio Network Controller (RNC) is a key 3G mobile network node that manages radio resources and controls multiple base stations within the UMTS radio access 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. UMTS core network
    The UMTS core network is the central backbone of 3G mobile systems, handling key functions such as call control, mobility management, and data routing between mobile users and external networks.
  • D. RLC (Radio Link Control) protocol for UMTS
    The RLC (Radio Link Control) protocol for UMTS is a Layer 2 protocol that provides segmentation, reassembly, error correction, and in-sequence delivery of data between the user equipment and the radio access network in 3G systems.
  • E. OsmoGGSN
    OsmoGGSN is an open-source GPRS Gateway Support Node implementation from the Osmocom project used to provide packet data connectivity in 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: RNC and SGSN (Iu‑U interface)
Target entity description: RNC and SGSN (Iu‑U interface) is the user-plane interface in 3G UMTS networks that carries packet-switched data traffic between the Radio Network Controller and the Serving GPRS Support Node.
  • A. Radio Network Controller (RNC)
    The Radio Network Controller (RNC) is a key 3G mobile network node that manages radio resources and controls multiple base stations within the UMTS radio access 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. UMTS core network
    The UMTS core network is the central backbone of 3G mobile systems, handling key functions such as call control, mobility management, and data routing between mobile users and external networks.
  • D. RLC (Radio Link Control) protocol for UMTS
    The RLC (Radio Link Control) protocol for UMTS is a Layer 2 protocol that provides segmentation, reassembly, error correction, and in-sequence delivery of data between the user equipment and the radio access network in 3G systems.
  • E. OsmoGGSN
    OsmoGGSN is an open-source GPRS Gateway Support Node implementation from the Osmocom project used to provide packet data connectivity in 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_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.