Triple

T28605087
Position Surface form Disambiguated ID Type / Status
Subject Highfield Park E724022 entity
Predicate locatedIn P40 FINISHED
Object Heckfield, Hampshire, England
Heckfield in Hampshire, England is a rural village and civil parish known for its historic country estates and parklands in the north of the county.
E1824228 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: Heckfield, Hampshire, England | Statement: [Highfield Park, locatedIn, Heckfield, Hampshire, England]
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: Heckfield, Hampshire, England
Triple: [Highfield Park, locatedIn, Heckfield, Hampshire, England]
Generated description
Heckfield in Hampshire, England is a rural village and civil parish known for its historic country estates and parklands in the north of the county.

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_69f01d816d7c8190a1fe27e3434041dc completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f65218a9548190a2e6bba4a7b20b65 completed May 2, 2026, 7:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cb705e778819081ab4722a7dd3c60 completed May 31, 2026, 10:32 p.m.
NEDg Description generation batch_6a1cb951b5a481908ffb688a5648a664 completed May 31, 2026, 10:42 p.m.
NED2 Entity disambiguation (via description) batch_6a1cb9c3e8e88190bf5c5955adf18073 completed May 31, 2026, 10:44 p.m.
Created at: April 28, 2026, 4:27 a.m.