Triple

T26323125
Position Surface form Disambiguated ID Type / Status
Subject Autoroute 55 E662169 entity
Predicate hasJunctionWith P1018 FINISHED
Object Route 143
Route 143 is a provincial highway in Quebec, Canada, that serves as a regional connector route intersecting with Autoroute 55.
E1726928 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 143 | Statement: [Autoroute 55, hasJunctionWith, Route 143]
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: Route 143
Triple: [Autoroute 55, hasJunctionWith, Route 143]
Generated description
Route 143 is a provincial highway in Quebec, Canada, that serves as a regional connector route intersecting with Autoroute 55.

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_69ee812e73048190aae587f1d51e5a06 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60f2cf8148190acaf42480d5abf0e completed May 2, 2026, 2:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11bb057f0c8190b115c42b8a547d1d completed May 23, 2026, 2:34 p.m.
NEDg Description generation batch_6a11bb7f64dc8190b0381d5225a30e62 completed May 23, 2026, 2:36 p.m.
NED2 Entity disambiguation (via description) batch_6a11be83120c819096ca5fc2f18a4739 completed May 23, 2026, 2:49 p.m.
Created at: April 26, 2026, 10:29 p.m.