Triple
T38204499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 673d Civil Engineer Group |
E1009159
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil engineer group |
C14887
|
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: civil engineer group Context triple: [673d Civil Engineer Group, instanceOf, civil engineer group]
-
A.
group of civil engineers
chosen
A group of civil engineers is a collaborative team of professionals who plan, design, and oversee the construction and maintenance of infrastructure projects such as roads, bridges, buildings, and water systems.
-
B.
engineering group
An engineering group is a coordinated team of engineers and related specialists who collaboratively design, develop, and maintain technical systems or products to meet specific organizational goals.
-
C.
civil engineer
A civil engineer is a professional who designs, constructs, and maintains infrastructure projects such as roads, bridges, buildings, and water systems to ensure safety, functionality, and sustainability.
-
D.
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.
-
E.
engineering firm
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.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.