Triple

T31065767
Position Surface form Disambiguated ID Type / Status
Subject Regional roads of Durham Region E791662 entity
Predicate hasComponent P35 FINISHED
Object Regional Road 80 (Durham Region)
Regional Road 80 is a numbered arterial roadway within Ontario’s Durham Region that forms part of the municipality’s regional road network.
E1949935 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: Regional Road 80 (Durham Region) | Statement: [Regional roads of Durham Region, hasComponent, Regional Road 80 (Durham Region)]
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: Regional Road 80 (Durham Region)
Triple: [Regional roads of Durham Region, hasComponent, Regional Road 80 (Durham Region)]
Generated description
Regional Road 80 is a numbered arterial roadway within Ontario’s Durham Region that forms part of the municipality’s regional road network.

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_69f224cc0c5c81908404f087bff92997 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6957aee008190a04d15daf49d5f08 completed May 3, 2026, 12:23 a.m.
NED1 Entity disambiguation (via context triple) batch_6a29470f821c8190a9445447b8eb2e14 completed June 10, 2026, 11:14 a.m.
NEDg Description generation batch_6a29482e8bc48190a1d257c7286b1ab1 completed June 10, 2026, 11:19 a.m.
NED2 Entity disambiguation (via description) batch_6a294eee82d48190a23f96b28727b881 completed June 10, 2026, 11:47 a.m.
Created at: April 29, 2026, 9:01 p.m.