Triple
T7944319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadcom |
E184462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infrastructure software company |
C18297
|
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: infrastructure software company Context triple: [Broadcom, instanceOf, infrastructure software company]
-
A.
infrastructure management company
An infrastructure management company plans, operates, maintains, and optimizes physical assets and systems—such as transportation, utilities, and public works—to ensure their reliability, efficiency, and long-term performance.
-
B.
automotive software company
A company that designs, develops, and maintains software solutions specifically for vehicles and the automotive industry, such as embedded systems, driver assistance, connectivity, and fleet management platforms.
-
C.
cloud services company
A cloud services company provides on-demand computing resources, storage, and software platforms over the internet, enabling organizations to scale and manage their IT infrastructure efficiently without owning physical hardware.
-
D.
computer services company
A computer services company is an organization that provides technical expertise, support, and solutions related to computer systems, software, networks, and IT infrastructure for individuals or other businesses.
-
E.
virtualization company
chosen
A virtualization company provides software and platforms that abstract and simulate computing resources—such as servers, storage, networks, or desktops—to enable more efficient, flexible, and scalable IT infrastructure.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:09 p.m.