Triple
T36761071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIMIC Group |
E908201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infrastructure contractor |
C64651
|
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 contractor Context triple: [CIMIC Group, instanceOf, infrastructure contractor]
-
A.
infrastructure construction company
chosen
An infrastructure construction company is an organization that plans, designs, and builds large-scale public and private works such as roads, bridges, tunnels, utilities, and related civil engineering projects.
-
B.
industrial contractor
An industrial contractor is a specialized company or individual responsible for planning, managing, and executing construction, installation, maintenance, or upgrade projects within industrial facilities such as factories, plants, and warehouses.
-
C.
pipeline construction company
A pipeline construction company is an organization that specializes in planning, designing, and building pipeline systems for transporting liquids or gases, often including related infrastructure and maintenance services.
-
D.
construction pioneer
A construction pioneer is an innovative leader who introduces groundbreaking methods, materials, or technologies that significantly advance how the built environment is designed and constructed.
-
E.
MEP contractor
An MEP contractor is a specialized construction professional or firm responsible for the design, coordination, installation, and maintenance of mechanical, electrical, and plumbing systems in buildings and infrastructure projects.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.