Triple
T30378828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles International Airport ground access network |
E772765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground access network |
C56836
|
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: ground access network Context triple: [Los Angeles International Airport ground access network, instanceOf, ground access network]
-
A.
municipal access network
A municipal access network is a city-managed telecommunications infrastructure that provides residents and businesses with local connectivity to broadband and related digital services.
-
B.
access point
An access point is a networking device that allows wireless devices to connect to a wired network, typically providing Wi-Fi connectivity within a specific area.
-
C.
gateway community access point
A gateway community access point is a centralized interface that connects local users or systems to broader networks, services, or resources, managing entry, security, and data flow between them.
-
D.
Radio access network architecture
Radio access network architecture is the structured design of hardware, software, and interfaces that connect user devices to the core network, defining how radio resources are organized, managed, and optimized.
-
E.
2G radio access network
A 2G radio access network is the collection of base stations, controllers, and related interfaces that provide digital cellular connectivity between mobile devices and the core network using second-generation (2G) wireless technologies such as GSM.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8 p.m.