Triple

T22109654
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 29.061 E546379 entity
Predicate relatedTo P37 FINISHED
Object 3GPP TS 23.060 — NE NERFINISHED

How this triple was built (2 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.060 | Statement: [3GPP TS 29.061, relatedTo, 3GPP TS 23.060]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 23.060
Context triple: [3GPP TS 29.061, relatedTo, 3GPP TS 23.060]
  • A. 3GPP TS 23.060 chosen
    3GPP TS 23.060 is a technical specification that defines the General Packet Radio Service (GPRS) architecture and procedures within 3GPP mobile networks.
  • B. 3GPP TS 29.060
    3GPP TS 29.060 is a technical specification that defines the GPRS Tunnelling Protocol (GTP) for the Gn and Gp interfaces in 3G mobile networks.
  • C. 3GPP TS 29.061
    3GPP TS 29.061 is a technical specification that defines the GPRS Tunnelling Protocol (GTP) and related interfaces for packet-switched core networks in mobile telecommunications systems.
  • D. 3GPP TS 23.002
    3GPP TS 23.002 is a technical specification that defines the overall network architecture and functional entities of mobile core networks in the 3GPP system.
  • E. 3GPP TS 23.040
    3GPP TS 23.040 is a 3rd Generation Partnership Project technical specification that defines the technical architecture, protocols, and procedures for Short Message Service (SMS) in mobile networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e11e378dc08190896d6a51597afd5a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1291b9c988190b3ddd06d1f40dc78 completed April 28, 2026, 9:39 p.m.
Created at: April 16, 2026, 8:30 p.m.