Triple
T21224307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARP (Allocation and Retention Priority) |
E523051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mobile network parameter |
C18456
|
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 network parameter Context triple: [ARP (Allocation and Retention Priority), instanceOf, Mobile network parameter]
-
A.
3GPP standardized parameter
chosen
A 3GPP standardized parameter is a formally defined technical value or setting specified by the 3rd Generation Partnership Project to ensure interoperability, performance, and compliance across mobile communication systems and equipment.
-
B.
data connectivity technology
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.
-
C.
mobile portal operator
A mobile portal operator is an entity that manages and delivers curated content, services, and applications to users through a centralized interface on mobile devices, often integrating billing, access control, and partnerships with content providers.
-
D.
wireless operator
A wireless operator is a person or system responsible for transmitting, receiving, and managing radio-based communications over wireless networks or devices.
-
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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:44 p.m.