Triple

T22847681
Position Surface form Disambiguated ID Type / Status
Subject TS 23-series E566266 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 23.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 23.107 | Statement: [TS 23-series, includes, 3GPP TS 23.107]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 23.107
Context triple: [TS 23-series, includes, 3GPP TS 23.107]
  • A. 3GPP TS 33.107
    3GPP TS 33.107 is a technical specification that defines security requirements and mechanisms for 3G mobile communication systems within the 3GPP standards framework.
  • B. 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.
  • C. 3GPP TS 22.071
    3GPP TS 22.071 is a technical specification that defines the service requirements and features for location services (LCS) in mobile communication systems.
  • D. 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.
  • E. 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.
  • 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 23.107
Target entity description: 3GPP TS 23.107 is a technical specification that defines the Quality of Service (QoS) concept and architecture for 3G and later mobile communication systems within the 3GPP framework.
  • A. 3GPP TS 33.107
    3GPP TS 33.107 is a technical specification that defines security requirements and mechanisms for 3G mobile communication systems within the 3GPP standards framework.
  • B. 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.
  • C. 3GPP TS 22.071
    3GPP TS 22.071 is a technical specification that defines the service requirements and features for location services (LCS) in mobile communication systems.
  • D. 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.
  • E. 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.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e89ab348190a31260221195ae67 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.