Triple
T5480700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serving Gateway |
E123459
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | eNodeB |
E522252
|
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: eNodeB | Statement: [Serving Gateway, connectsTo, eNodeB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: eNodeB Context triple: [Serving Gateway, connectsTo, eNodeB]
-
A.
eNodeB
chosen
eNodeB is the base station in LTE networks responsible for radio transmission, reception, and control functions between user devices and the core network.
-
B.
Home eNodeB Gateway
A Home eNodeB Gateway is a core network element in LTE that aggregates and manages traffic and signaling from multiple residential or enterprise femtocell base stations (Home eNodeBs) to the operator’s core network.
-
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.
gNB
gNB (next-generation Node B) is the 5G New Radio base station that provides radio access and connectivity between user equipment and the 5G core network.
-
E.
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.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd924a2eb08190b759b23a6eab5e0a |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf70d919e08190a4fae4359cf8c951 |
completed | March 22, 2026, 4:32 a.m. |
Created at: March 20, 2026, 2:09 p.m.