Triple
T33956888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NJ 28 |
E870600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numbered route in New Jersey |
C36899
|
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 route in New Jersey Context triple: [NJ 28, instanceOf, numbered route in New Jersey]
-
A.
numbered highway in New Jersey
chosen
A numbered highway in New Jersey is a designated roadway within the state’s transportation network, identified by a unique route number and maintained by state or federal agencies to facilitate regional and interstate travel.
-
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.
numbered highway in New Hampshire
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.
-
D.
numbered highway in Pennsylvania
A numbered highway in Pennsylvania is a designated roadway within the state’s transportation network identified by a unique route number and maintained by state or federal authorities for regional and interstate travel.
-
E.
numbered highway in Maryland
A numbered highway in Maryland is a designated roadway within the state’s transportation network, identified by a unique route number and maintained by the appropriate state or federal agency to facilitate regional and interstate travel.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.