Triple
T22929177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Routes in New Jersey |
E569387
|
entity |
| Predicate | hasFormerRoute |
P102403
|
FINISHED |
| Object | U.S. Route 30 Bypass in New Jersey |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: U.S. Route 30 Bypass in New Jersey | Statement: [U.S. Routes in New Jersey, hasFormerRoute, U.S. Route 30 Bypass in New Jersey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 30 Bypass in New Jersey Context triple: [U.S. Routes in New Jersey, hasFormerRoute, U.S. Route 30 Bypass in New Jersey]
-
A.
U.S. Route 1 Alternate in New Jersey
U.S. Route 1 Alternate in New Jersey was a former auxiliary highway that provided an alternate alignment to the main U.S. Route 1 corridor within the state.
-
B.
New Jersey Route 33 Alternate
New Jersey Route 33 Alternate is a former state highway in New Jersey that served as an alternate alignment to the main Route 33, typically routing traffic through more local or urban areas.
-
C.
New Jersey Route 18 regional connector
The New Jersey Route 18 regional connector is a roadway segment that links local streets in East Brunswick to the larger Route 18 highway, facilitating regional traffic flow in central New Jersey.
-
D.
U.S. Route 30 in New Jersey
U.S. Route 30 in New Jersey is a major east–west highway that runs from the Pennsylvania state line near Camden to Atlantic City, serving as a key route across southern New Jersey.
-
E.
New Jersey Route 413
New Jersey Route 413 is a short state highway in Burlington County that connects the city of Burlington to the Burlington–Bristol Bridge and Pennsylvania Route 413 across the Delaware River.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 30 Bypass in New Jersey Target entity description: U.S. Route 30 Bypass in New Jersey was a former auxiliary alignment of U.S. Route 30 that diverted through traffic around more congested local sections of the main highway in the state.
-
A.
U.S. Route 1 Alternate in New Jersey
U.S. Route 1 Alternate in New Jersey was a former auxiliary highway that provided an alternate alignment to the main U.S. Route 1 corridor within the state.
-
B.
New Jersey Route 33 Alternate
New Jersey Route 33 Alternate is a former state highway in New Jersey that served as an alternate alignment to the main Route 33, typically routing traffic through more local or urban areas.
-
C.
New Jersey Route 18 regional connector
The New Jersey Route 18 regional connector is a roadway segment that links local streets in East Brunswick to the larger Route 18 highway, facilitating regional traffic flow in central New Jersey.
-
D.
U.S. Route 30 in New Jersey
U.S. Route 30 in New Jersey is a major east–west highway that runs from the Pennsylvania state line near Camden to Atlantic City, serving as a key route across southern New Jersey.
-
E.
New Jersey Route 413
New Jersey Route 413 is a short state highway in Burlington County that connects the city of Burlington to the Burlington–Bristol Bridge and Pennsylvania Route 413 across the Delaware River.
- F. None of above. chosen
Provenance (2 batches)
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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180dc33e8819099e5ad87207de57f |
completed | April 29, 2026, 3:54 a.m. |
Created at: April 17, 2026, 3:44 p.m.