Triple

T19605270
Position Surface form Disambiguated ID Type / Status
Subject Township of Carlstadt E470588 entity
Predicate locatedNear P294 FINISHED
Object Route 17 — NE NERFINISHED

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 17 | Statement: [Township of Carlstadt, locatedNear, Route 17]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Route 17
Context triple: [Township of Carlstadt, locatedNear, Route 17]
  • A. Route 17 chosen
    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.
  • 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 18
    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.
  • 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 (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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e640c6cb3c819096b8093499d8e1ad completed April 20, 2026, 3:05 p.m.
Created at: April 10, 2026, 1:43 p.m.