Triple
T2130634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Transportation Cabinet |
E46530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation department |
C3209
|
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 department Context triple: [Kentucky Transportation Cabinet, instanceOf, transportation department]
-
A.
transport ministry
chosen
The transport ministry is a government department responsible for planning, regulating, and overseeing a nation’s transportation systems and infrastructure, including roads, railways, air, and maritime transport.
-
B.
transportation organization
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
-
C.
transportation safety agency
A transportation safety agency is an organization responsible for regulating, monitoring, and enforcing safety standards across transportation systems to prevent accidents and protect the public.
-
D.
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.
-
E.
public transit safety oversight agency
A public transit safety oversight agency is a governmental or quasi-governmental body responsible for setting, monitoring, and enforcing safety standards and practices across public transportation systems to protect passengers, workers, and the public.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:44 p.m.