Triple
T38329014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UrbaCon Trading & Contracting |
E1036868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contracting company |
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: contracting company Context triple: [UrbaCon Trading & Contracting, instanceOf, contracting company]
-
A.
construction firm
A construction firm is a business organization that plans, manages, and executes building and infrastructure projects, coordinating labor, materials, equipment, and subcontractors to deliver completed structures for clients.
-
B.
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.
-
C.
international contracting group
An international contracting group is an organization that coordinates, negotiates, and manages contracts across multiple countries, ensuring compliance with diverse legal, regulatory, and commercial frameworks.
-
D.
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.
-
E.
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.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.