Triple
T35860810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Street runs diagonally across the city grid |
E1036941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street alignment description |
C36041
|
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: street alignment description Context triple: [Market Street runs diagonally across the city grid, instanceOf, street alignment description]
-
A.
road alignment
chosen
Road alignment is the planned horizontal and vertical positioning of a roadway’s centerline to achieve safe, efficient, and economical traffic movement within given terrain and design constraints.
-
B.
road designation
A road designation is a label or code assigned to a roadway (such as a route number, name, or classification) that identifies its function, hierarchy, and navigational role within a transportation network.
-
C.
civic thoroughfare
A civic thoroughfare is a major public street or corridor designed to accommodate high volumes of movement while structuring and showcasing key civic, cultural, and institutional functions of a community.
-
D.
street address
A street address uniquely identifies the location of a building or property within a city or region using elements such as house number, street name, unit or apartment number, city, state or province, postal code, and country.
-
E.
street
A street is a public thoroughfare in an urban or suburban area, typically bordered by buildings, that facilitates vehicular and pedestrian movement and often supports various social and commercial activities.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.