Triple
T9731475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hampshire Route 10A |
E235752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numbered highway 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: numbered highway in New Hampshire Context triple: [New Hampshire Route 10A, instanceOf, numbered highway in New Hampshire]
-
A.
numbered highway in Maine
A numbered highway in Maine is a designated state, U.S., or interstate route identified by a unique number that provides organized, signed road connections between cities, towns, and regions within and beyond the state.
-
B.
numbered highway in New York
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).
-
C.
U.S. Numbered Highway
A U.S. Numbered Highway is a nationally coordinated, signed roadway within the United States that is part of the United States Numbered Highway System, providing intercity and interstate connections but distinct from the Interstate Highway System.
-
D.
numbered highway in Tennessee
A numbered highway in Tennessee is a designated state or U.S. route within Tennessee’s road network, identified by a unique number and maintained for regional and interstate transportation.
-
E.
highway numbering policy
Highway numbering policy is the set of rules and conventions that govern how route numbers are assigned, organized, and displayed across a road network to convey location, hierarchy, and direction.
- F. None of above. chosen
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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:22 p.m.