Triple

T21306224
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 23.501 E525204 entity
Predicate defines P264 FINISHED
Object Location Management Function — 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: Location Management Function | Statement: [3GPP TS 23.501, defines, Location Management Function]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Location Management Function
Context triple: [3GPP TS 23.501, defines, Location Management Function]
  • A. 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.
  • B. 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.
  • C. Mobility Management (MM) protocol
    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.
  • D. Mobile Switching Centre
    The Mobile Switching Centre is a central GSM network component that manages call setup, routing, and mobility control for mobile subscribers within its service area.
  • 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: Location Management Function
Target entity description: The Location Management Function (LMF) is a 5G core network function responsible for providing positioning and location services for user equipment based on 3GPP specifications.
  • A. 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.
  • B. 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.
  • C. Mobility Management (MM) protocol
    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.
  • D. Mobile Switching Centre
    The Mobile Switching Centre is a central GSM network component that manages call setup, routing, and mobility control for mobile subscribers within its service area.
  • 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_69e0b518b8948190ad69cf9a8784d397 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75aa52a508190bb5dc806b6483574 completed April 21, 2026, 11:08 a.m.
Created at: April 16, 2026, 4:05 p.m.