Triple

T23081813
Position Surface form Disambiguated ID Type / Status
Subject TS 28-series E575494 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 28.040 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 28.040 | Statement: [TS 28-series, includes, 3GPP TS 28.040]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 28.040
Context triple: [TS 28-series, includes, 3GPP TS 28.040]
  • A. 3GPP TS 28.004
    3GPP TS 28.004 is a technical specification within the 3GPP 28-series that defines operations, administration, and maintenance (OAM) aspects for mobile telecommunications networks.
  • B. 3GPP TS 28.401
    3GPP TS 28.401 is a technical specification that defines management and orchestration aspects of mobile telecommunications networks within the 3GPP standards framework.
  • C. 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.
  • D. 3GPP TS 28.104
    3GPP TS 28.104 is a technical specification that defines the operation and maintenance requirements for radio network equipment in mobile telecommunications systems.
  • E. 3GPP TS 28.300
    3GPP TS 28.300 is a technical specification that defines the architecture and principles for telecommunications management within 3GPP 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 28.040
Target entity description: 3GPP TS 28.040 is a technical specification that defines operations, administration, and maintenance (OAM) aspects for mobile telecommunications networks within the 3GPP standards framework.
  • A. 3GPP TS 28.004
    3GPP TS 28.004 is a technical specification within the 3GPP 28-series that defines operations, administration, and maintenance (OAM) aspects for mobile telecommunications networks.
  • B. 3GPP TS 28.401
    3GPP TS 28.401 is a technical specification that defines management and orchestration aspects of mobile telecommunications networks within the 3GPP standards framework.
  • C. 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.
  • D. 3GPP TS 28.104
    3GPP TS 28.104 is a technical specification that defines the operation and maintenance requirements for radio network equipment in mobile telecommunications systems.
  • E. 3GPP TS 28.300
    3GPP TS 28.300 is a technical specification that defines the architecture and principles for telecommunications management within 3GPP 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_69e245be28d48190ad1348d5a73db37d completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18da239e48190ad041261c6b510a0 completed April 29, 2026, 4:48 a.m.
Created at: April 17, 2026, 3:56 p.m.