Triple

T16970586
Position Surface form Disambiguated ID Type / Status
Subject Harnham E411663 entity
Predicate hasSubdivision P747 FINISHED
Object East Harnham E411663 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: East Harnham | Statement: [Harnham, hasSubdivision, East Harnham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: East Harnham
Context triple: [Harnham, hasSubdivision, East Harnham]
  • A. Harnham chosen
    Harnham is a suburb of Salisbury in Wiltshire, England, known for its historic buildings and scenic riverside setting near Salisbury Cathedral.
  • B. Haddenham
    Haddenham is a large village in Buckinghamshire, England, known for its historic architecture and rural setting near the town of Thame.
  • C. Haddenham
    Haddenham is a village and civil parish in Cambridgeshire, England, known for its rural character and historic parish church.
  • D. Farningham
    Farningham is a historic village in the Sevenoaks District of Kent, England, known for its rural character and location on the River Darent.
  • E. Fakenham Magna
    Fakenham Magna is a small rural village and civil parish located in the county of Suffolk in eastern England.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0ac23a48190992fa125fceb1eb2 completed April 18, 2026, 6:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a011b3f751c81908906ec969bef55c5 completed May 10, 2026, 11:56 p.m.
Created at: April 10, 2026, 5:31 a.m.