Triple
T25412357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Cambridge street design standards |
E636735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation planning standard |
C5735
|
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 standard Context triple: [City of Cambridge street design standards, instanceOf, transportation planning standard]
-
A.
transportation standard
chosen
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.
-
B.
metropolitan transportation planning instrument
A metropolitan transportation planning instrument is a formal tool or framework used to analyze, coordinate, and guide long-term transportation investments and policies across an urbanized region.
-
C.
AASHTO policy document
An AASHTO policy document is an official publication by the American Association of State Highway and Transportation Officials that establishes standards, guidelines, and best practices for the planning, design, construction, and operation of transportation infrastructure in the United States.
-
D.
regional transport plan
A regional transport plan is a strategic framework that outlines long-term goals, policies, and coordinated investments for transportation systems across a defined geographic region.
-
E.
spatial planning instrument
A spatial planning instrument is a formal tool, policy, or regulatory mechanism used by authorities to guide, control, and coordinate the use and development of land and space within a defined territory.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:55 p.m.