Triple

T21226606
Position Surface form Disambiguated ID Type / Status
Subject Network Slice Instance E523098 entity
Predicate specifiedIn P775 FINISHED
Object 3GPP TS 28.530 — 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 28.530 | Statement: [Network Slice Instance, specifiedIn, 3GPP TS 28.530]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 28.530
Context triple: [Network Slice Instance, specifiedIn, 3GPP TS 28.530]
  • A. 3GPP TS 29.531
    3GPP TS 29.531 is a 3rd Generation Partnership Project technical specification that defines the network functions and service-based interfaces related to the Network Slice Selection Function (NSSF) in 5G core networks.
  • B. 3GPP TS 31.130
    3GPP TS 31.130 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM/USIM applications in mobile communication systems.
  • C. 3GPP TS 29.500
    3GPP TS 29.500 is a technical specification that defines the 5G Core Network Service-Based Architecture (SBA) principles and related control-plane interfaces within the 3GPP standards.
  • D. 3GPP TS 29.510
    3GPP TS 29.510 is a 3rd Generation Partnership Project technical specification that defines the service-based interface and procedures for the Network Repository Function (NRF) within 5G core networks.
  • E. 3GPP TS 25.322
    3GPP TS 25.322 is a 3rd Generation Partnership Project technical specification that defines the Radio Link Control (RLC) layer procedures and protocols used in UMTS WCDMA 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 28.530
Target entity description: 3GPP TS 28.530 is a 3GPP technical specification that defines management and orchestration aspects of 5G network slicing, including the lifecycle and configuration of network slice instances.
  • A. 3GPP TS 29.531
    3GPP TS 29.531 is a 3rd Generation Partnership Project technical specification that defines the network functions and service-based interfaces related to the Network Slice Selection Function (NSSF) in 5G core networks.
  • B. 3GPP TS 31.130
    3GPP TS 31.130 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM/USIM applications in mobile communication systems.
  • C. 3GPP TS 29.500
    3GPP TS 29.500 is a technical specification that defines the 5G Core Network Service-Based Architecture (SBA) principles and related control-plane interfaces within the 3GPP standards.
  • D. 3GPP TS 29.510
    3GPP TS 29.510 is a 3rd Generation Partnership Project technical specification that defines the service-based interface and procedures for the Network Repository Function (NRF) within 5G core networks.
  • E. 3GPP TS 25.322
    3GPP TS 25.322 is a 3rd Generation Partnership Project technical specification that defines the Radio Link Control (RLC) layer procedures and protocols used in UMTS WCDMA 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734ab3f6c819083e277ea1c33134e completed April 21, 2026, 8:26 a.m.
Created at: April 16, 2026, 3:44 p.m.