Triple

T5848855
Position Surface form Disambiguated ID Type / Status
Subject 3GPP CT4 E129977 entity
Predicate relatedTo P37 FINISHED
Object Evolved Packet Core E127334 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: Evolved Packet Core | Statement: [3GPP CT4, relatedTo, Evolved Packet Core]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Evolved Packet Core
Context triple: [3GPP CT4, relatedTo, Evolved Packet Core]
  • A. Evolved Packet Core chosen
    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.
  • B. 5G Core
    5G Core is the cloud-native, service-based core network architecture that underpins 5G mobile systems, enabling advanced connectivity, slicing, and low-latency services.
  • C. E-UTRAN
    E-UTRAN is the LTE mobile network’s air-interface subsystem that connects user devices to the core network via evolved base stations (eNodeBs).
  • D. GSM core network
    The GSM core network is the central backbone of GSM mobile systems, handling key functions such as switching, mobility management, authentication, and interconnection with other networks.
  • E. eNodeB
    eNodeB is the base station in LTE networks responsible for radio transmission, reception, and control functions between user devices and the core network.
  • 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_69c0084de39081909eb34e6bed74215a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c035145a0c8190941945a83a3f2416 completed March 22, 2026, 6:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0a1b052288190ace51e65f1d888ab completed March 23, 2026, 2:13 a.m.
Created at: March 22, 2026, 3:55 p.m.