Triple

T21192562
Position Surface form Disambiguated ID Type / Status
Subject RLC (Radio Link Control) protocol for UMTS E522246 entity
Predicate specifiedIn P775 FINISHED
Object 3GPP TS 25.322 — 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 25.322 | Statement: [RLC (Radio Link Control) protocol for UMTS, specifiedIn, 3GPP TS 25.322]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 25.322
Context triple: [RLC (Radio Link Control) protocol for UMTS, specifiedIn, 3GPP TS 25.322]
  • A. 3GPP TS 23.272
    3GPP TS 23.272 is a 3rd Generation Partnership Project technical specification that defines the system architecture and procedures enabling circuit-switched services for LTE/EPC networks, including mechanisms such as Circuit Switched Fallback.
  • B. 3GPP TS 24.302
    3GPP TS 24.302 is a technical specification that defines the non-access stratum (NAS) signaling procedures for evolved packet system (EPS) emergency and public warning services in mobile networks.
  • C. 3GPP TS 23.502
    3GPP TS 23.502 is a 5G system architecture specification that defines procedures and interactions between core network functions for access, mobility, and session management.
  • D. 3GPP TS 36.321
    3GPP TS 36.321 is a technical specification that defines the Medium Access Control (MAC) protocol for the LTE (E-UTRA) radio interface in 3GPP mobile networks.
  • E. 3GPP TS 31.122
    3GPP TS 31.122 is a technical specification defining aspects of the interface and behavior of UICC/SIM applications in mobile communication systems within the 3GPP standards framework.
  • 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 25.322
Target entity description: 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.
  • A. 3GPP TS 23.272
    3GPP TS 23.272 is a 3rd Generation Partnership Project technical specification that defines the system architecture and procedures enabling circuit-switched services for LTE/EPC networks, including mechanisms such as Circuit Switched Fallback.
  • B. 3GPP TS 24.302
    3GPP TS 24.302 is a technical specification that defines the non-access stratum (NAS) signaling procedures for evolved packet system (EPS) emergency and public warning services in mobile networks.
  • C. 3GPP TS 23.502
    3GPP TS 23.502 is a 5G system architecture specification that defines procedures and interactions between core network functions for access, mobility, and session management.
  • D. 3GPP TS 36.321
    3GPP TS 36.321 is a technical specification that defines the Medium Access Control (MAC) protocol for the LTE (E-UTRA) radio interface in 3GPP mobile networks.
  • E. 3GPP TS 31.122
    3GPP TS 31.122 is a technical specification defining aspects of the interface and behavior of UICC/SIM applications in mobile communication systems within the 3GPP standards framework.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73338dbe881908360dedad65c964b completed April 21, 2026, 8:20 a.m.
Created at: April 16, 2026, 3:07 p.m.