Triple
T25412356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Cambridge street design standards |
E636735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal street design guideline |
C37106
|
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: municipal street design guideline Context triple: [City of Cambridge street design standards, instanceOf, municipal street design guideline]
-
A.
roadway safety guideline
A roadway safety guideline is a documented set of principles, rules, and recommended practices designed to minimize traffic-related risks and enhance the safety of all road users.
-
B.
municipal policy framework
chosen
A municipal policy framework is a structured set of principles, regulations, and procedures that guide a city or local government's decision-making, service delivery, and long-term planning.
-
C.
urban design element
An urban design element is a physical or spatial feature—such as streets, plazas, parks, or street furniture—that shapes the form, function, and experience of the urban environment.
-
D.
urban design project
An urban design project is a coordinated planning and design effort that shapes the physical form, public spaces, infrastructure, and land use of a specific urban area to improve its functionality, aesthetics, and livability.
-
E.
architectural guidance document series
A curated, structured collection of documents that provide consistent principles, patterns, and recommendations to guide architectural decisions across related projects or domains.
- 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.