Triple
T34318103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. O’Rourke & Son |
E880650
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | construction firm |
C65480
|
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 firm Context triple: [R. O’Rourke & Son, instanceOf, construction firm]
-
A.
construction conglomerate
A construction conglomerate is a large, diversified corporate group that owns and manages multiple construction-related companies across sectors such as infrastructure, real estate, engineering, and industrial projects.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
infrastructure construction company
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.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.