Triple

T23042163
Position Surface form Disambiguated ID Type / Status
Subject TS 27-series E573765 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 27.018 — 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 27.018 | Statement: [TS 27-series, includes, 3GPP TS 27.018]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 27.018
Context triple: [TS 27-series, includes, 3GPP TS 27.018]
  • A. 3GPP TS 31.801
    3GPP TS 31.801 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM-related functions in mobile communication systems.
  • B. 3GPP TS 29.518
    3GPP TS 29.518 is a 3rd Generation Partnership Project technical specification that defines the service-based interface and procedures between the Access and Mobility Management Function (AMF) and other 5G core network functions.
  • C. 3GPP TS 27.008
    3GPP TS 27.008 is a technical specification that defines the AT command set and control interface between mobile equipment and terminal adapters in 3GPP mobile communication systems.
  • D. 3GPP TS 22.185
    3GPP TS 22.185 is a 3rd Generation Partnership Project technical specification that defines service requirements for a particular telecommunications capability within the TS 22-series.
  • E. 3GPP TS 26.118
    3GPP TS 26.118 is a technical specification that defines the IP Multimedia Subsystem (IMS)–based telephony and multimedia communication services, including media handling and signaling aspects, 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 27.018
Target entity description: 3GPP TS 27.018 is a technical specification defining aspects of terminal–network communication behavior within the 3GPP TS 27-series for mobile telecommunications systems.
  • A. 3GPP TS 31.801
    3GPP TS 31.801 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM-related functions in mobile communication systems.
  • B. 3GPP TS 29.518
    3GPP TS 29.518 is a 3rd Generation Partnership Project technical specification that defines the service-based interface and procedures between the Access and Mobility Management Function (AMF) and other 5G core network functions.
  • C. 3GPP TS 27.008
    3GPP TS 27.008 is a technical specification that defines the AT command set and control interface between mobile equipment and terminal adapters in 3GPP mobile communication systems.
  • D. 3GPP TS 22.185
    3GPP TS 22.185 is a 3rd Generation Partnership Project technical specification that defines service requirements for a particular telecommunications capability within the TS 22-series.
  • E. 3GPP TS 26.118
    3GPP TS 26.118 is a technical specification that defines the IP Multimedia Subsystem (IMS)–based telephony and multimedia communication services, including media handling and signaling aspects, 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_69e245b9c11481909d06c872214d21af completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18516417081908bf747b20de23a75 completed April 29, 2026, 4:12 a.m.
Created at: April 17, 2026, 3:54 p.m.