Triple
T5481335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSM core network |
E123472
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GSM system component |
C1322
|
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: GSM system component Context triple: [GSM core network, instanceOf, GSM system component]
-
A.
telecommunications infrastructure component
chosen
A telecommunications infrastructure component is a physical or virtual element—such as cables, antennas, switches, or routers—that enables the transmission, routing, and management of voice, data, and multimedia communications across networks.
-
B.
telecommunications network
A telecommunications network is a system of interconnected nodes, transmission media, and protocols that enables the exchange of voice, data, and multimedia information between users and devices over distance.
-
C.
wireless communication device
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
D.
telecommunications standard
A telecommunications standard is an agreed-upon set of technical specifications and protocols that ensure compatibility, interoperability, and reliable communication across different telecom networks and devices.
-
E.
internet infrastructure component
An internet infrastructure component is a foundational hardware or software element—such as routers, switches, servers, cables, or protocols—that enables the transmission, routing, and reliable delivery of data across interconnected networks.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:09 p.m.