Triple
T5771447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 29-series |
E127338
|
entity |
| Predicate | usedIn |
P98
|
FINISHED |
| Object | 4G EPC |
E23870
|
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: 4G EPC | Statement: [3GPP TS 29-series, usedIn, 4G EPC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 4G EPC Context triple: [3GPP TS 29-series, usedIn, 4G EPC]
-
A.
ePDG
ePDG (Evolved Packet Data Gateway) is a core network element in LTE/4G that securely connects users over untrusted non-3GPP access networks, such as public Wi‑Fi, to the mobile operator’s EPC.
-
B.
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).
-
C.
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.
-
D.
eNodeB
eNodeB is the base station in LTE networks responsible for radio transmission, reception, and control functions between user devices and the core network.
-
E.
EPC
chosen
EPC (Evolved Packet Core) is the all-IP mobile core network architecture defined by 3GPP for 4G LTE systems, enabling high-speed data, voice, and multimedia services.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029ac21ec81908d88ba72e966d7cb |
completed | March 22, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07e648aa881908411a00d48998ecc |
completed | March 22, 2026, 11:42 p.m. |
Created at: March 22, 2026, 3:50 p.m.