Triple
T35065351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron (pressure control and processing) |
E1011714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flow control technology company |
C63089
|
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: flow control technology company Context triple: [Cameron (pressure control and processing), instanceOf, flow control technology company]
-
A.
embedded systems company
An embedded systems company designs, develops, and integrates specialized hardware and software solutions that perform dedicated functions within larger electronic products and devices.
-
B.
networking technology company
A networking technology company designs, develops, and delivers hardware, software, and services that enable reliable, secure, and high-performance data communication between devices, systems, and networks.
-
C.
digital infrastructure company
A digital infrastructure company designs, builds, and operates the foundational technology systems—such as data centers, networks, cloud platforms, and connectivity services—that enable digital applications and services to function reliably and at scale.
-
D.
air traffic management systems manufacturer
A company that designs, develops, and produces integrated systems and technologies used to monitor, control, and optimize the safe and efficient movement of aircraft in airspace and at airports.
-
E.
industrial automation company
An industrial automation company designs, develops, and implements control systems, robotics, and software solutions to optimize and automate manufacturing and industrial processes.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.