Triple
T20614618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth Transportation Board |
E506533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state transportation board |
C43356
|
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 board Context triple: [Commonwealth Transportation Board, instanceOf, state transportation board]
-
A.
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.
-
B.
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.
-
C.
state highway
A state highway is a public road maintained and administered by a state government, forming part of a regional or statewide transportation network that connects cities, towns, and other major routes.
-
D.
California state board
A California state board is an official governing or advisory body established by state law to oversee, regulate, or provide guidance on specific public policy areas, professions, or services within California.
-
E.
state highway system
A state highway system is a network of roads and highways maintained and regulated by a state government to facilitate regional transportation and connectivity.
- F. None of above. chosen
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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.