Triple

T6402563
Position Surface form Disambiguated ID Type / Status
Subject 3GPP E144097 entity
Predicate standardizes P1371 FINISHED
Object 5G Core E23871 NE FINISHED

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: 5G Core | Statement: [3GPP, standardizes, 5G Core]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 5G Core
Context triple: [3GPP, standardizes, 5G Core]
  • A. 5G Core chosen
    5G Core is the cloud-native, service-based core network architecture that underpins 5G mobile systems, enabling advanced connectivity, slicing, and low-latency services.
  • B. Evolved Packet Core
    Evolved Packet Core is the 4G LTE mobile network architecture responsible for managing data connectivity, mobility, and services between user devices and external IP networks.
  • C. NG-RAN
    NG-RAN is the 5G New Radio access network architecture specified by 3GPP, encompassing gNodeBs and their interfaces to the 5G core.
  • D. 5G NR
    5G NR is the global 5G wireless communication standard defined by 3GPP, designed to deliver significantly higher data rates, lower latency, and greater capacity than previous mobile network technologies.
  • E. 3GPP Core Network and Terminals (CT)
    3GPP Core Network and Terminals (CT) is a technical specification group within 3GPP responsible for defining standards for core network architectures, protocols, and terminal interfaces in mobile communication systems.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c008dc56fc81908d43ffcc11d73bdd completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c068ade8c881908a0472f1de6b7c21 completed March 22, 2026, 10:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69c638a6e6248190bda7ad3fbd8f4746 completed March 27, 2026, 7:58 a.m.
Created at: March 22, 2026, 4:35 p.m.