Triple
T14869406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strassenverkehrsamt des Kantons Zürich |
E349703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cantonal road traffic authority |
C10843
|
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: cantonal road traffic authority Context triple: [Strassenverkehrsamt des Kantons Zürich, instanceOf, cantonal road traffic authority]
-
A.
traffic authority
chosen
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
-
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.
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.
departmental road
A departmental road is a public roadway managed and maintained by a specific administrative department or local authority, typically serving regional or intra-departmental traffic rather than national or major arterial routes.
-
E.
toll road operator
A toll road operator is an entity responsible for managing, maintaining, and collecting user fees on designated roadways or bridges, often under government concession or private ownership.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:55 a.m.