Triple

T13585130
Position Surface form Disambiguated ID Type / Status
Subject Kedington E324532 entity
Predicate near P350 FINISHED
Object Haverhill E321821 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: Haverhill | Statement: [Kedington, near, Haverhill]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haverhill
Context triple: [Kedington, near, Haverhill]
  • A. Haverhill
    Haverhill is a historic city in northeastern Massachusetts that functions as a suburban community within the Greater Boston metropolitan area.
  • B. Haverhill chosen
    Haverhill is a market town in Suffolk, England, known for its growing population, light industry, and role as a commuter hub for nearby larger cities.
  • C. Ipswich
    Ipswich is a historic city in South East Queensland, Australia, known for its heritage architecture and role as a major residential and industrial hub west of Brisbane.
  • D. Ipswich
    Ipswich is a historic town and port in Suffolk, England, known as one of the country’s oldest continuously inhabited settlements.
  • E. Chelmsford
    Chelmsford is a suburban town in northeastern Massachusetts known for its residential communities, local history, and proximity to the city of Lowell.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d80769100c819099111274614f5ed2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb03310fc819092a56b9f2d73f560 completed April 12, 2026, 2:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f79d3f80c081908710b46a42fb13a3 completed May 3, 2026, 7:08 p.m.
Created at: April 9, 2026, 9:49 p.m.