Triple

T22941348
Position Surface form Disambiguated ID Type / Status
Subject TS 24-series E569736 entity
Predicate hasMember P10 FINISHED
Object 3GPP TS 24.237 — 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 24.237 | Statement: [TS 24-series, hasMember, 3GPP TS 24.237]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 24.237
Context triple: [TS 24-series, hasMember, 3GPP TS 24.237]
  • A. 3GPP TS 24.173
    3GPP TS 24.173 is a technical specification defining the stage 3 protocol and procedures for the IP Multimedia Subsystem (IMS) Multimedia Telephony service in mobile networks.
  • B. 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.
  • C. 3GPP TS 29.274
    3GPP TS 29.274 is a technical specification that defines the GPRS Tunnelling Protocol (GTPv2-C) for control plane signaling between core network nodes in 4G LTE and related mobile networks.
  • D. 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.
  • E. 3GPP TS 23.203
    3GPP TS 23.203 is a 3GPP technical specification that defines the policy and charging control architecture and mechanisms for QoS management in mobile networks.
  • 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 24.237
Target entity description: 3GPP TS 24.237 is a technical specification within the 3GPP 24-series that defines signaling and protocol procedures at the service layer for IP-based multimedia and telecommunication services in mobile networks.
  • A. 3GPP TS 24.173
    3GPP TS 24.173 is a technical specification defining the stage 3 protocol and procedures for the IP Multimedia Subsystem (IMS) Multimedia Telephony service in mobile networks.
  • B. 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.
  • C. 3GPP TS 29.274
    3GPP TS 29.274 is a technical specification that defines the GPRS Tunnelling Protocol (GTPv2-C) for control plane signaling between core network nodes in 4G LTE and related mobile networks.
  • D. 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.
  • E. 3GPP TS 23.203
    3GPP TS 23.203 is a 3GPP technical specification that defines the policy and charging control architecture and mechanisms for QoS management in mobile networks.
  • 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_69e24590862c8190858f180ad302adab completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181394fec81909da791bb346dbd0a completed April 29, 2026, 3:55 a.m.
Created at: April 17, 2026, 3:45 p.m.