Triple

T23081821
Position Surface form Disambiguated ID Type / Status
Subject TS 28-series E575494 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 28.310 — 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.310 | Statement: [TS 28-series, includes, 3GPP TS 28.310]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 3GPP TS 28.310
Context triple: [TS 28-series, includes, 3GPP TS 28.310]
  • A. 3GPP TS 33.310
    3GPP TS 33.310 is a technical specification that defines security architecture and procedures for authentication, key management, and certificate handling in 3G mobile and LTE networks.
  • B. 3GPP TS 28.010
    3GPP TS 28.010 is a technical specification that defines the principles and guidelines for operations, administration, and maintenance (OAM) of mobile telecommunications networks within the 3GPP standards framework.
  • C. 3GPP TS 28.531
    3GPP TS 28.531 is a 3GPP technical specification that defines management and orchestration aspects of 5G network slicing, including the lifecycle and operations of Network Slice Instances.
  • D. 3GPP TS 28.530
    3GPP TS 28.530 is a 3GPP technical specification that defines management and orchestration aspects of 5G network slicing, including the lifecycle and configuration of network slice instances.
  • E. 3GPP TS 36.410
    3GPP TS 36.410 is a technical specification that defines the architecture, functions, and interfaces of the Home eNodeB Gateway within LTE 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.310
Target entity description: 3GPP TS 28.310 is a technical specification that defines operations, administration, and maintenance (OAM) requirements and interfaces for mobile telecommunications networks within the 3GPP standards framework.
  • A. 3GPP TS 33.310
    3GPP TS 33.310 is a technical specification that defines security architecture and procedures for authentication, key management, and certificate handling in 3G mobile and LTE networks.
  • B. 3GPP TS 28.010
    3GPP TS 28.010 is a technical specification that defines the principles and guidelines for operations, administration, and maintenance (OAM) of mobile telecommunications networks within the 3GPP standards framework.
  • C. 3GPP TS 28.531
    3GPP TS 28.531 is a 3GPP technical specification that defines management and orchestration aspects of 5G network slicing, including the lifecycle and operations of Network Slice Instances.
  • D. 3GPP TS 28.530
    3GPP TS 28.530 is a 3GPP technical specification that defines management and orchestration aspects of 5G network slicing, including the lifecycle and configuration of network slice instances.
  • E. 3GPP TS 36.410
    3GPP TS 36.410 is a technical specification that defines the architecture, functions, and interfaces of the Home eNodeB Gateway within LTE 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.