Triple
T4031797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5ESS switch |
E83730
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital telecommunications switching system |
C13792
|
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: digital telecommunications switching system Context triple: [5ESS switch, instanceOf, digital telecommunications switching system]
-
A.
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.
-
B.
telephone exchange
chosen
A telephone exchange is a system or facility that connects telephone calls by switching voice or data signals between subscribers on a telecommunications network.
-
C.
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.
-
D.
telecommunications infrastructure component
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.
-
E.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:36 p.m.