Triple
T17556079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transportation Engineering Agency |
E427593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation engineering organization |
C4656
|
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: transportation engineering organization Context triple: [Transportation Engineering Agency, instanceOf, transportation engineering organization]
-
A.
transportation organization
chosen
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
-
B.
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.
-
C.
transportation research program
A transportation research program is an organized initiative that systematically studies and develops knowledge, technologies, and policies to improve the safety, efficiency, sustainability, and equity of transportation systems.
-
D.
AASHTO committee
An AASHTO committee is a collaborative body within the American Association of State Highway and Transportation Officials that develops, reviews, and recommends standards, policies, and best practices for transportation systems in the United States.
-
E.
systems engineering organization
A systems engineering organization is a structured group that plans, designs, integrates, and manages complex systems across their life cycles to meet stakeholder needs within technical, cost, and schedule constraints.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.