Triple
T27911099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Transportation Commission |
E705930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state transportation commission |
C3980
|
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: state transportation commission Context triple: [Oregon Transportation Commission, instanceOf, state transportation commission]
-
A.
state transportation board
A state transportation board is a governing body that oversees planning, funding, and policy decisions for a state’s transportation systems and infrastructure.
-
B.
state transport department
A state transport department is a government agency responsible for planning, regulating, and managing transportation systems and infrastructure within a state, including roads, public transit, and vehicle services.
-
C.
division of a state transportation department
A division of a state transportation department is an organizational unit responsible for managing specific functions—such as planning, construction, maintenance, or safety—within the broader mission of developing and operating the state's transportation system.
-
D.
interstate council
An interstate council is a formal collaborative body composed of representatives from multiple states or jurisdictions that coordinates policies, resolves shared issues, and facilitates joint decision-making across state boundaries.
-
E.
state government commission
chosen
A state government commission is an officially authorized body established by a state to investigate, regulate, advise on, or administer specific public policy areas or functions within its jurisdiction.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:50 p.m.