Triple

T21276068
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 24.008 E524389 entity
Predicate governs P760 FINISHED
Object Mobility Management (MM) protocol — 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: Mobility Management (MM) protocol | Statement: [3GPP TS 24.008, governs, Mobility Management (MM) protocol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Mobility Management (MM) protocol
Context triple: [3GPP TS 24.008, governs, Mobility Management (MM) protocol]
  • A. Mobility Management Entity
    The Mobility Management Entity is a core LTE network component responsible for user mobility, session management, and signaling control between user devices and the network.
  • B. 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.
  • C. MME
    MME is the IATA airport code for Teesside International Airport, serving the Teesside and County Durham region in northeast England.
  • 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. 3GPP Policy and Charging Control architecture specifications
    The 3GPP Policy and Charging Control architecture specifications define the standardized framework, interfaces, and rules for managing network policy, quality of service, and charging in mobile communication systems.
  • 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: Mobility Management (MM) protocol
Target entity description: The Mobility Management (MM) protocol is a core 3GPP signaling protocol that handles user registration, location updating, and mobility-related procedures for mobile devices in cellular networks.
  • A. Mobility Management Entity
    The Mobility Management Entity is a core LTE network component responsible for user mobility, session management, and signaling control between user devices and the network.
  • B. 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.
  • C. MME
    MME is the IATA airport code for Teesside International Airport, serving the Teesside and County Durham region in northeast England.
  • 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. 3GPP Policy and Charging Control architecture specifications
    The 3GPP Policy and Charging Control architecture specifications define the standardized framework, interfaces, and rules for managing network policy, quality of service, and charging in mobile communication systems.
  • 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_69e0b516293c819089458ea2ec85f85e completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736577fd48190a0038a6ac5678668 completed April 21, 2026, 8:33 a.m.
Created at: April 16, 2026, 4:02 p.m.