Triple
T9783166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Planning (Kentucky Transportation Cabinet) |
E237425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation planning 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 planning organization Context triple: [Division of Planning (Kentucky Transportation Cabinet), instanceOf, transportation planning 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.
regional planning agency
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic region.
-
C.
public transportation agency
A public transportation agency is an organization responsible for planning, operating, and managing shared transit services such as buses, trains, and other modes to provide mobility for the public within a defined region.
-
D.
planning agency
A planning agency is an organization responsible for developing, coordinating, and regulating plans and policies to guide land use, infrastructure, and community development within a specific jurisdiction.
-
E.
planning commission
A planning commission is a governmental or advisory body responsible for reviewing, guiding, and making recommendations on land use, development proposals, and long-term community planning policies.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:27 p.m.