Triple

T26656289
Position Surface form Disambiguated ID Type / Status
Subject Orleans County, Vermont E666514 entity
Predicate hasTown P847 FINISHED
Object Westmore, Vermont
Westmore, Vermont is a small rural town in northeastern Vermont known for its scenic landscapes and outdoor recreation in the Northeast Kingdom region.
E1916476 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: Westmore, Vermont | Statement: [Orleans County, Vermont, hasTown, Westmore, Vermont]
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: Westmore, Vermont
Triple: [Orleans County, Vermont, hasTown, Westmore, Vermont]
Generated description
Westmore, Vermont is a small rural town in northeastern Vermont known for its scenic landscapes and outdoor recreation in the Northeast Kingdom region.

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_69ee9cf8c7188190b9b00270a8a89164 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6168101b881909d4c2c6ca31180a8 completed May 2, 2026, 3:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27abf2b6548190a83d020ed3856859 completed June 9, 2026, 6 a.m.
NEDg Description generation batch_6a27acae789081908a0500ce5b46b481 completed June 9, 2026, 6:03 a.m.
NED2 Entity disambiguation (via description) batch_6a27ad6a946c8190a4d6aafcb235849d completed June 9, 2026, 6:06 a.m.
Created at: April 27, 2026, 2:35 a.m.