Triple

T17272854
Position Surface form Disambiguated ID Type / Status
Subject Lavaltrie E419307 entity
Predicate locatedOnTransportRoute P2409 FINISHED
Object Route 131 E1039338 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 131 | Statement: [Lavaltrie, locatedOnTransportRoute, Route 131]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route 131
Context triple: [Lavaltrie, locatedOnTransportRoute, Route 131]
  • A. Route 131 chosen
    Route 131 is a provincial highway in Quebec, Canada, that serves as a key north–south transportation corridor through the Lanaudière region.
  • B. Route 136
    Route 136 is a state highway in southwestern Connecticut that runs through coastal communities and connects several local and regional routes.
  • C. Route 136
    Route 136 is an urban highway in Montreal that serves as a key east–west connector through the city’s central road network.
  • D. Route 130
    Route 130 is a major north–south state highway in New Jersey that serves as an important alternative to the New Jersey Turnpike and U.S. Route 1 for regional traffic.
  • E. Route 132
    Route 132 is a state highway in Pennsylvania that serves as a key east–west arterial road through suburban communities.
  • 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_69d886da626481908a14ce7830329a35 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42f4b023c8190b92df4015c14c3a8 completed April 19, 2026, 1:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0195488d2c81908ac6c19f54f61796 completed May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:40 a.m.