Triple
T21227333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gateway Mobile Switching Centre |
E523116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile switching centre |
C44400
|
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 switching centre Context triple: [Gateway Mobile Switching Centre, instanceOf, mobile switching centre]
-
A.
mobile satellite service system
A mobile satellite service system is a communication network that uses satellites to provide voice, data, and messaging connectivity to mobile users over wide geographic areas, including remote and underserved regions.
-
B.
mobility management protocol
A mobility management protocol is a set of rules and procedures that enables devices to maintain seamless network connectivity and consistent addressing while moving across different networks or access points.
-
C.
switching and terminal company
A switching and terminal company is a railroad entity that specializes in transferring railcars between different rail lines and managing terminal operations within a specific geographic area or rail hub.
-
D.
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.
-
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. 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:44 p.m.