Triple

T26780992
Position Surface form Disambiguated ID Type / Status
Subject Autoroute 440 (Laval) E670244 entity
Predicate connectsWith P37 FINISHED
Object Boulevard Curé-Labelle
Boulevard Curé-Labelle is a major north–south arterial road in Laval, Quebec, serving as a key commercial and transportation corridor through the city.
E1754726 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: Boulevard Curé-Labelle | Statement: [Autoroute 440 (Laval), connectsWith, Boulevard Curé-Labelle]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Boulevard Curé-Labelle
Triple: [Autoroute 440 (Laval), connectsWith, Boulevard Curé-Labelle]
Generated description
Boulevard Curé-Labelle is a major north–south arterial road in Laval, Quebec, serving as a key commercial and transportation corridor through the city.

Provenance (5 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_69eeb31c925881909b597f6e40056d28 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f6197ad524819086c1e2de6a3b52a9 completed May 2, 2026, 3:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a123a99fe0c81908a0df61553f0add8 completed May 23, 2026, 11:39 p.m.
NEDg Description generation batch_6a123c7ffbd081909b2b2dd40996ca4b completed May 23, 2026, 11:47 p.m.
NED2 Entity disambiguation (via description) batch_6a123cda13308190bba2e6edd51fa924 completed May 23, 2026, 11:48 p.m.
Created at: April 27, 2026, 4:09 a.m.