Triple
T4214303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomson-CSF Racal |
E93976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | communications equipment manufacturer |
C7642
|
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: communications equipment manufacturer Context triple: [Thomson-CSF Racal, instanceOf, communications equipment manufacturer]
-
A.
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.
-
B.
networking hardware company
chosen
A networking hardware company designs, manufactures, and sells physical devices and infrastructure that enable data communication and connectivity across computer networks.
-
C.
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.
-
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 entrepreneur
A telecommunications entrepreneur is an individual who identifies opportunities and builds businesses that develop, provide, or innovate communication networks, services, or technologies connecting people and organizations.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:04 p.m.