Triple

T22107477
Position Surface form Disambiguated ID Type / Status
Subject Alberta Highway 11 E546322 entity
Predicate hasJunctionWith P1018 FINISHED
Object Highway 20
Highway 20 is a provincial highway in Alberta, Canada, that serves communities in the central part of the province and connects with several major routes.
E2293754 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: Highway 20 | Statement: [Alberta Highway 11, hasJunctionWith, Highway 20]
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: Highway 20
Triple: [Alberta Highway 11, hasJunctionWith, Highway 20]
Generated description
Highway 20 is a provincial highway in Alberta, Canada, that serves communities in the central part of the province and connects with several major routes.

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_69e11e378dc08190896d6a51597afd5a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1291adc74819092c7753bb6f3768d completed April 28, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7afd228fc881908aa2ab1d65780489 completed Aug. 11, 2026, 10:44 a.m.
NEDg Description generation batch_6a7afda9ece88190a8f2f8595e65bba1 completed Aug. 11, 2026, 10:47 a.m.
NED2 Entity disambiguation (via description) batch_6a7afe5db64c819083285d2fca8c6ded completed Aug. 11, 2026, 10:50 a.m.
Created at: April 16, 2026, 8:30 p.m.