Triple
T35078990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinci Energies |
E1012381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering and services company |
C426
|
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: engineering and services company Context triple: [Vinci Energies, instanceOf, engineering and services company]
-
A.
oil and gas services company
An oil and gas services company provides specialized technical, operational, and logistical support to exploration and production firms across the hydrocarbon value chain.
-
B.
engineering firm
chosen
An engineering firm is a business organization that provides professional engineering services—such as design, analysis, consulting, and project management—to plan, develop, and implement technical solutions for clients in various industries.
-
C.
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.
-
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.
environmental services company
An environmental services company is an organization that provides specialized solutions to manage, protect, and restore natural resources and ecosystems through activities such as waste management, pollution control, remediation, and sustainability consulting.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.