Triple
T11530195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Report on Roads and Canals |
E273397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation policy document |
C19343
|
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 policy document Context triple: [Report on Roads and Canals, instanceOf, transportation policy document]
-
A.
transport policy framework
chosen
A transport policy framework is a structured set of principles, goals, and regulatory tools that guide the planning, funding, operation, and governance of transportation systems to achieve economic, social, and environmental objectives.
-
B.
transport policy body
A transport policy body is an organization or authority responsible for developing, coordinating, and overseeing regulations, strategies, and standards that govern transportation systems and services.
-
C.
transportation standard
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
-
D.
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.
-
E.
federal transportation safety guidance
Federal transportation safety guidance comprises the policies, recommendations, and standards issued by national authorities to prevent accidents, protect public welfare, and ensure safe operation across all modes of transportation.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:37 p.m.