Triple

T34326547
Position Surface form Disambiguated ID Type / Status
Subject Boxford, Massachusetts E880878 entity
Predicate hasHistoricBuilding P1098 FINISHED
Object Holyoke–French House
The Holyoke–French House is a historic residence in Boxford, Massachusetts, notable for its early New England architecture and association with prominent local families.
E2091753 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: Holyoke–French House | Statement: [Boxford, Massachusetts, hasHistoricBuilding, Holyoke–French House]
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: Holyoke–French House
Triple: [Boxford, Massachusetts, hasHistoricBuilding, Holyoke–French House]
Generated description
The Holyoke–French House is a historic residence in Boxford, Massachusetts, notable for its early New England architecture and association with prominent local families.

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_69f349b9cd508190a996a616903b3e6d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71393d8fc81909f4ba3bc6ffe5565 completed May 3, 2026, 9:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36f9d5ae2081908b86e6e435ca46bd completed June 20, 2026, 8:36 p.m.
NEDg Description generation batch_6a36fb468d248190ada52608298a4ef2 completed June 20, 2026, 8:42 p.m.
NED2 Entity disambiguation (via description) batch_6a36fbdbfd7881909e5088bedded00a3 completed June 20, 2026, 8:45 p.m.
Created at: May 1, 2026, 1:58 a.m.