Triple
T16235424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Transport Department, Haryana |
E394096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state transport department |
C37157
|
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 transport department Context triple: [State Transport Department, Haryana, instanceOf, state transport department]
-
A.
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.
-
B.
transport ministry
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.
-
C.
state police agency
A state police agency is a government law enforcement organization with statewide jurisdiction responsible for enforcing laws, maintaining public order, and supporting local agencies across the entire state.
-
D.
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.
-
E.
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.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.