Triple
T24760860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hampshire Route 152 |
E619435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in New Hampshire |
C27180
|
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 Hampshire Context triple: [New Hampshire Route 152, instanceOf, road in New Hampshire]
-
A.
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.
-
B.
numbered highway in New Hampshire
chosen
A numbered highway in New Hampshire is a designated state, U.S., or interstate route within New Hampshire’s road network, identified by a unique number and maintained by the appropriate transportation authority.
-
C.
road in Nova Scotia
A road in Nova Scotia is a constructed transportation route, ranging from major highways to local streets, that connects communities across the province and supports the movement of people, goods, and services.
-
D.
road in Virginia
A road in Virginia is a designated vehicular travelway within the Commonwealth of Virginia that facilitates transportation, access, and connectivity between locations while adhering to state and local regulations and infrastructure standards.
-
E.
road in Salem, Massachusetts
A road in Salem, Massachusetts is a public thoroughfare that provides vehicular and pedestrian access through the city, connecting residential, commercial, and historic areas while integrating with local traffic regulations and infrastructure.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:27 a.m.