Triple
T13268004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Route 34 (New York) |
E315973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in New York |
C22420
|
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: road in New York Context triple: [County Route 34 (New York), instanceOf, road in New York]
-
A.
street in New York City
A street in New York City is a public urban thoroughfare lined with diverse buildings and infrastructure that supports vehicular, pedestrian, and commercial activity within the city's dense grid layout.
-
B.
road in Shanghai
A road in Shanghai is a transportation corridor within the city’s dense urban fabric that supports mixed traffic—vehicles, buses, bicycles, and pedestrians—while integrating local infrastructure, commercial activity, and municipal regulations specific to Shanghai.
-
C.
numbered highway in New York
chosen
A numbered highway in New York is a designated, signed roadway within the state’s transportation network, identified by a unique route number and maintained by a specific governmental authority (state, federal, or local).
-
D.
road in New Brunswick
A road in New Brunswick is a designated transportation corridor within the province that facilitates vehicular travel between communities, regions, and key destinations, following provincial standards for construction, maintenance, and signage.
-
E.
road in Baltimore
A road in Baltimore is a public thoroughfare within the city’s transportation network that facilitates vehicular, bicycle, and pedestrian movement while connecting neighborhoods, businesses, and regional routes.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:25 p.m.