Triple

T21192738
Position Surface form Disambiguated ID Type / Status
Subject NR E522250 entity
Predicate usesCoreNetwork P6820 FINISHED
Object 5G Core (5GC) 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: 5G Core (5GC) | Statement: [NR, usesCoreNetwork, 5G Core (5GC)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 5G Core (5GC)
Context triple: [NR, usesCoreNetwork, 5G Core (5GC)]
  • 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 SA
    3GPP SA (Service and System Aspects) is the working group within the 3rd Generation Partnership Project responsible for overall system architecture, service requirements, and cross-domain coordination for mobile communication standards.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73338dbe881908360dedad65c964b completed April 21, 2026, 8:20 a.m.
Created at: April 16, 2026, 3:07 p.m.