Triple

T23747548
Position Surface form Disambiguated ID Type / Status
Subject Hildene, Manchester, Vermont, United States E586859 entity
Predicate city P40 FINISHED
Object Manchester
Manchester is a small, historic town in southwestern Vermont known for its scenic Green Mountain setting, outlet shopping, and nearby outdoor recreation.
E1579296 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: Manchester | Statement: [Hildene, Manchester, Vermont, United States, city, Manchester]
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: Manchester
Triple: [Hildene, Manchester, Vermont, United States, city, Manchester]
Generated description
Manchester is a small, historic town in southwestern Vermont known for its scenic Green Mountain setting, outlet shopping, and nearby outdoor recreation.

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_69e24908efb08190bf755c3a9b91f222 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bcbef1e481909fb49427dbd76460 completed April 29, 2026, 8:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f696b2bf08190b6cfc375ca7d5e79 completed May 21, 2026, 8:22 p.m.
NEDg Description generation batch_6a0f6d3de27c8190b3cab02a1dfce6ae completed May 21, 2026, 8:38 p.m.
NED2 Entity disambiguation (via description) batch_6a0f6e2ff6c481909b81c0d31259a919 completed May 21, 2026, 8:42 p.m.
Created at: April 17, 2026, 7:12 p.m.