Triple
T23853649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiewit Infrastructure West Co. |
E592242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | construction company subsidiary |
C46410
|
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: construction company subsidiary Context triple: [Kiewit Infrastructure West Co., instanceOf, construction company subsidiary]
-
A.
construction technology company
A construction technology company develops and provides digital tools, software, and innovative systems that improve the planning, design, management, and execution of construction projects.
-
B.
construction and trading company
A construction and trading company is a business entity that both executes building and infrastructure projects and engages in the procurement, sale, and distribution of construction-related materials, equipment, or goods.
-
C.
construction management firm
A construction management firm is a professional organization that plans, coordinates, and oversees construction projects from inception to completion, ensuring they are delivered on time, within budget, and to specified quality and safety standards.
-
D.
road construction company
chosen
A road construction company is an organization that plans, designs, builds, repairs, and maintains roads and related infrastructure for public and private clients.
-
E.
bridge construction company
A bridge construction company is a specialized engineering and construction firm that plans, designs, and builds bridges, managing all phases from feasibility studies and structural design to on-site construction and maintenance.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:11 p.m.