Triple

T24106670
Position Surface form Disambiguated ID Type / Status
Subject Vermont–Quebec border E597243 entity
Predicate crossedBy P416 FINISHED
Object Vermont Route 139
Vermont Route 139 is a short state highway in northern Vermont that connects the town of Richford to the Canadian border, where it continues as Quebec Route 139.
 E1643795 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: Vermont Route 139 | Statement: [Vermont–Quebec border, crossedBy, Vermont Route 139]
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: Vermont Route 139
Triple: [Vermont–Quebec border, crossedBy, Vermont Route 139]
Generated description
Vermont Route 139 is a short state highway in northern Vermont that connects the town of Richford to the Canadian border, where it continues as Quebec Route 139.

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_69e288c60f9c8190af948d7354aedbeb completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1de170ee88190a6d57482651f7da9 completed April 29, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1004538b9081908ba9dfd62568fad8 completed May 22, 2026, 7:22 a.m.
NEDg Description generation batch_6a1006551694819093b1927defd99fa6 completed May 22, 2026, 7:31 a.m.
NED2 Entity disambiguation (via description) batch_6a1006c065cc81908af8ae63739b4c37 completed May 22, 2026, 7:33 a.m.
Created at: April 17, 2026, 11:01 p.m.