Triple
T34542052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abis |
E886829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile telecommunications interface |
C59219
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: mobile telecommunications interface Context triple: [Abis, instanceOf, mobile telecommunications interface]
-
A.
mobile network interface
A mobile network interface is a hardware and software component that enables a device to connect to and communicate over cellular networks for voice, data, and messaging services.
-
B.
IMT-2000 radio interface
An IMT-2000 radio interface is a standardized third-generation (3G) mobile communication air interface specification that defines how user equipment and networks exchange radio signals to provide global, interoperable wireless voice and data services.
-
C.
mobile data terminal
A mobile data terminal is a rugged, portable computing device used in vehicles or field environments to send, receive, and display data over wireless communication networks.
-
D.
mobile core network protocol
A mobile core network protocol is a set of standardized rules and procedures that govern how data, signaling, and control information are exchanged within the core of a mobile communication network to enable connectivity, mobility, and services for users.
-
E.
mobile network security specification family
A mobile network security specification family is a cohesive set of standards and guidelines that define security requirements, protocols, and mechanisms to protect mobile communication networks, their infrastructure, and user data.
- F. None of above. chosen
Provenance (1 batch)
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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.