Triple

T22430099
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 33-series E554474 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 33.122 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 33.122 | Statement: [3GPP TS 33-series, includes, 3GPP TS 33.122]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 33.122
Context triple: [3GPP TS 33-series, includes, 3GPP TS 33.122]
  • A. 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.
  • B. 3GPP TS 36.322
    3GPP TS 36.322 is a 3GPP technical specification that defines the Radio Link Control (RLC) protocol for LTE (E-UTRA) radio interface communications.
  • C. 3GPP TS 33.102
    3GPP TS 33.102 is a technical specification that defines the security architecture and mechanisms for 3G (UMTS) mobile networks.
  • D. 3GPP TS 33.127
    3GPP TS 33.127 is a technical specification defining security requirements and mechanisms for lawful interception in 3GPP mobile communication systems.
  • E. 3GPP TS 33.220
    3GPP TS 33.220 is a 3GPP technical specification that defines security mechanisms and architecture for the Bootstrapping Server Function (BSF) and related network entities 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: 3GPP TS 33.122
Target entity description: 3GPP TS 33.122 is a technical specification that defines security aspects and requirements for certain mobile telecommunications services within the 3GPP standards framework.
  • A. 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.
  • B. 3GPP TS 36.322
    3GPP TS 36.322 is a 3GPP technical specification that defines the Radio Link Control (RLC) protocol for LTE (E-UTRA) radio interface communications.
  • C. 3GPP TS 33.102
    3GPP TS 33.102 is a technical specification that defines the security architecture and mechanisms for 3G (UMTS) mobile networks.
  • D. 3GPP TS 33.127
    3GPP TS 33.127 is a technical specification defining security requirements and mechanisms for lawful interception in 3GPP mobile communication systems.
  • E. 3GPP TS 33.220
    3GPP TS 33.220 is a 3GPP technical specification that defines security mechanisms and architecture for the Bootstrapping Server Function (BSF) and related network entities 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_69e11e4f2d0c819091aa3558ea2ee630 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15a311b148190bdb752f3f067bb3f completed April 29, 2026, 1:09 a.m.
Created at: April 16, 2026, 8:47 p.m.