Triple
T17663076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Systra |
E440300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering and consulting firm |
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 consulting firm Context triple: [Systra, instanceOf, engineering and consulting firm]
-
A.
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.
-
B.
architecture and design firm
A professional company that plans, designs, and often oversees the construction of buildings and interior spaces, integrating aesthetics, functionality, and client needs.
-
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.
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.
civil engineering support organization
A civil engineering support organization is an entity that provides specialized technical, logistical, administrative, and project management services to assist civil engineers and infrastructure projects throughout their lifecycle.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 9:51 a.m.