Triple

T29145744
Position Surface form Disambiguated ID Type / Status
Subject Haney E738765 entity
Predicate roadAccessVia P9041 FINISHED
Object Dewdney Trunk Road
Dewdney Trunk Road is a major historic east–west arterial route in British Columbia’s Lower Mainland, connecting several communities including the Haney area of Maple Ridge.
E1863664 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: Dewdney Trunk Road | Statement: [Haney, roadAccessVia, Dewdney Trunk Road]
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: Dewdney Trunk Road
Triple: [Haney, roadAccessVia, Dewdney Trunk Road]
Generated description
Dewdney Trunk Road is a major historic east–west arterial route in British Columbia’s Lower Mainland, connecting several communities including the Haney area of Maple Ridge.

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_69f07cb46f148190874eb8576a447567 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f66271fc4c81908824de34290609d6 completed May 2, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25c0d489cc8190b28755e645157c90 completed June 7, 2026, 7:04 p.m.
NEDg Description generation batch_6a25c5e70d9481909ca844a606a58fca completed June 7, 2026, 7:26 p.m.
NED2 Entity disambiguation (via description) batch_6a25c6477ea8819084543ee70fa03ca4 completed June 7, 2026, 7:28 p.m.
Created at: April 28, 2026, 11:39 a.m.