Triple

T21224082
Position Surface form Disambiguated ID Type / Status
Subject ViLTE E523046 entity
Predicate definedInStandardSeries P5655 FINISHED
Object 3GPP TS 26.114 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 26.114 | Statement: [ViLTE, definedInStandardSeries, 3GPP TS 26.114]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 26.114
Context triple: [ViLTE, definedInStandardSeries, 3GPP TS 26.114]
  • A. 3GPP TS 31.140
    3GPP TS 31.140 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM/USIM applications in mobile communication systems.
  • B. 3GPP TS 26.441
    3GPP TS 26.441 is a 3rd Generation Partnership Project technical specification that defines the detailed codec description and implementation guidelines for the Enhanced Voice Services (EVS) audio codec used in modern mobile communication systems.
  • C. 3GPP TS 31.143
    3GPP TS 31.143 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM-related features in mobile communication systems.
  • D. 3GPP TS 29.214
    3GPP TS 29.214 is a 3rd Generation Partnership Project technical specification that defines the policy and charging control signaling procedures and interfaces between core network elements in mobile communication systems.
  • E. 3GPP TS 36.214
    3GPP TS 36.214 is a technical specification that defines the physical layer measurements and performance requirements for LTE (E-UTRA) radio 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 26.114
Target entity description: 3GPP TS 26.114 is a technical specification that defines the IP multimedia subsystem (IMS) multimedia telephony service, including voice and video over LTE and related media handling.
  • A. 3GPP TS 31.140
    3GPP TS 31.140 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM/USIM applications in mobile communication systems.
  • B. 3GPP TS 26.441
    3GPP TS 26.441 is a 3rd Generation Partnership Project technical specification that defines the detailed codec description and implementation guidelines for the Enhanced Voice Services (EVS) audio codec used in modern mobile communication systems.
  • C. 3GPP TS 31.143
    3GPP TS 31.143 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior of UICC/SIM-related features in mobile communication systems.
  • D. 3GPP TS 29.214
    3GPP TS 29.214 is a 3rd Generation Partnership Project technical specification that defines the policy and charging control signaling procedures and interfaces between core network elements in mobile communication systems.
  • E. 3GPP TS 36.214
    3GPP TS 36.214 is a technical specification that defines the physical layer measurements and performance requirements for LTE (E-UTRA) radio 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734a9c9f88190817b574f916886e5 completed April 21, 2026, 8:26 a.m.
Created at: April 16, 2026, 3:44 p.m.