Triple

T22430086
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 33-series E554474 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 33.107 — 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.107 | Statement: [3GPP TS 33-series, includes, 3GPP TS 33.107]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 33.107
Context triple: [3GPP TS 33-series, includes, 3GPP TS 33.107]
  • A. 3GPP TS 32.270
    3GPP TS 32.270 is a technical specification that defines the charging data record (CDR) transfer and management mechanisms for mobile telecommunications networks within the 3GPP standards framework.
  • B. 3GPP TS 33.102
    3GPP TS 33.102 is a technical specification that defines the security architecture and mechanisms for 3G (UMTS) mobile networks.
  • C. 3GPP TS 33.106
    3GPP TS 33.106 is a technical specification within the 3GPP security series that defines security requirements and mechanisms for mobile telecommunications systems.
  • D. 3GPP TS 31.103
    3GPP TS 31.103 is a technical specification that defines the characteristics and requirements for USIM (Universal Subscriber Identity Module) applications used in 3G and LTE mobile networks.
  • E. 3GPP TS 32.273
    3GPP TS 32.273 is a technical specification within the 3GPP 32-series that defines aspects of telecommunications network management and operations for mobile 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.107
Target entity description: 3GPP TS 33.107 is a technical specification that defines security requirements and mechanisms for 3G mobile communication systems within the 3GPP standards framework.
  • A. 3GPP TS 32.270
    3GPP TS 32.270 is a technical specification that defines the charging data record (CDR) transfer and management mechanisms for mobile telecommunications networks within the 3GPP standards framework.
  • B. 3GPP TS 33.102
    3GPP TS 33.102 is a technical specification that defines the security architecture and mechanisms for 3G (UMTS) mobile networks.
  • C. 3GPP TS 33.106
    3GPP TS 33.106 is a technical specification within the 3GPP security series that defines security requirements and mechanisms for mobile telecommunications systems.
  • D. 3GPP TS 31.103
    3GPP TS 31.103 is a technical specification that defines the characteristics and requirements for USIM (Universal Subscriber Identity Module) applications used in 3G and LTE mobile networks.
  • E. 3GPP TS 32.273
    3GPP TS 32.273 is a technical specification within the 3GPP 32-series that defines aspects of telecommunications network management and operations for mobile 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.