Triple

T12517860
Position Surface form Disambiguated ID Type / Status
Subject Route 29 (New Jersey) E299234 entity
Predicate hasJunctionWith P1018 FINISHED
Object New Jersey Route 179 — 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: New Jersey Route 179 | Statement: [Route 29 (New Jersey), hasJunctionWith, New Jersey Route 179]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: New Jersey Route 179
Context triple: [Route 29 (New Jersey), hasJunctionWith, New Jersey Route 179]
  • A. New Jersey Route 173
    New Jersey Route 173 is a state highway in western New Jersey that runs through rural and suburban areas, serving as a local parallel route to Interstate 78.
  • B. New Jersey Route 175
    New Jersey Route 175 is a short state highway in New Jersey that serves as a local parallel route to portions of New Jersey Route 29, primarily in the Trenton area.
  • C. New Jersey Route 172
    New Jersey Route 172 is a short state highway serving as a local connector in New Brunswick, primarily providing access between Route 18 and nearby Rutgers University and city streets.
  • D. New Jersey Route 183
    New Jersey Route 183 is a short state highway in northern New Jersey that serves as a local connector through communities such as Stanhope, following a former alignment of U.S. Route 206.
  • E. New Jersey Route 139
    New Jersey Route 139 is an elevated state highway in Jersey City that serves as a key connector between the New Jersey Turnpike, U.S. Route 1/9, and the Holland Tunnel into Lower Manhattan.
  • 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: New Jersey Route 179
Target entity description: New Jersey Route 179 is a state highway in central New Jersey that serves as a local connector through the Lambertville–Ringoes area, largely following a former alignment of U.S. Route 202.
  • A. New Jersey Route 173
    New Jersey Route 173 is a state highway in western New Jersey that runs through rural and suburban areas, serving as a local parallel route to Interstate 78.
  • B. New Jersey Route 175
    New Jersey Route 175 is a short state highway in New Jersey that serves as a local parallel route to portions of New Jersey Route 29, primarily in the Trenton area.
  • C. New Jersey Route 172
    New Jersey Route 172 is a short state highway serving as a local connector in New Brunswick, primarily providing access between Route 18 and nearby Rutgers University and city streets.
  • D. New Jersey Route 183
    New Jersey Route 183 is a short state highway in northern New Jersey that serves as a local connector through communities such as Stanhope, following a former alignment of U.S. Route 206.
  • E. New Jersey Route 139
    New Jersey Route 139 is an elevated state highway in Jersey City that serves as a key connector between the New Jersey Turnpike, U.S. Route 1/9, and the Holland Tunnel into Lower Manhattan.
  • 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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9545a2e188190bb92120df740003d completed April 10, 2026, 7:49 p.m.
Created at: April 8, 2026, 9:57 p.m.