Triple
T22233113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSPA |
E549518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile broadband technology family |
C9032
|
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 broadband technology family Context triple: [HSPA, instanceOf, mobile broadband technology family]
-
A.
data connectivity technology
chosen
Data connectivity technology encompasses the tools, protocols, and infrastructure that enable seamless, secure, and reliable exchange of data between systems, applications, and devices across diverse networks and environments.
-
B.
mobile network feature set
A mobile network feature set is the collection of capabilities, services, and performance characteristics (such as voice, data, messaging, security, and quality-of-service options) provided by a mobile communication network to its users and connected devices.
-
C.
family of digital subscriber line technologies
A family of digital subscriber line technologies is a group of related high-speed data transmission methods that use existing telephone lines to deliver broadband internet and other digital services.
-
D.
IMT-2000 family member
An IMT-2000 family member is a mobile communication system that conforms to the ITU’s IMT-2000 (3G) standards, ensuring global interoperability, high-speed data, and advanced multimedia services.
-
E.
mobile phone line
A mobile phone line is a telecommunications service subscription that assigns a unique phone number and network access to a mobile device for voice, text, and data communication.
- F. None of above.
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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:38 p.m.