Triple

T9167626
Position Surface form Disambiguated ID Type / Status
Subject County Route 537 E220000 entity
Predicate crosses P416 FINISHED
Object Route 18 E674526 NE FINISHED

How this triple was built (2 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: Route 18 | Statement: [County Route 537, crosses, Route 18]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Route 18
Context triple: [County Route 537, crosses, Route 18]
  • A. Route 18 chosen
    Route 18 is a major state highway in central New Jersey that serves as a key north–south corridor connecting communities such as New Brunswick and Sayreville.
  • B. Route 17
    Route 17 is a state highway designation in Massachusetts used for a specific segment of roadway within the state's numbered route system.
  • C. Route 17
    Route 17 is a major state highway in New York that serves as a key transportation corridor through the southern part of the state, connecting numerous towns and villages.
  • D. Route 16
    Route 16 is a major roadway in northern Chile that connects the inland city of Alto Hospicio with the coastal port city of Iquique.
  • E. Route 16
    Route 16 is a major east–west state highway in Massachusetts that connects several cities and towns in the Greater Boston area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca83e467108190abcae6a33b3d4dad completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccaadfb50881909b9127f92e4b3e21 completed April 1, 2026, 5:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05c077f008190ba1bcd82b3fe9a1d completed April 4, 2026, 12:32 a.m.
Created at: March 30, 2026, 7:22 p.m.