Triple

T16580942
Position Surface form Disambiguated ID Type / Status
Subject Ruskington E402827 entity
Predicate nearbyVillage P4647 FINISHED
Object Leasingham E552941 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: Leasingham | Statement: [Ruskington, nearbyVillage, Leasingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leasingham
Context triple: [Ruskington, nearbyVillage, Leasingham]
  • A. Leasingham chosen
    Leasingham is a small village and civil parish in the South Kesteven district of Lincolnshire, England.
  • B. Elsenham
    Elsenham is a village and civil parish in the Uttlesford district of Essex, England, known for its rural character and railway station on the West Anglia Main Line.
  • C. Immingham
    Immingham is a major port town on the Humber Estuary in North East Lincolnshire, England, known for its large freight docks and industrial facilities.
  • D. Wintringham
    Wintringham is an English surname associated with figures such as Tom Wintringham, a notable British soldier, politician, and writer.
  • E. Cleethorpes
    Cleethorpes is a seaside resort town on the east coast of England, known for its sandy beaches, promenade, and traditional British holiday attractions.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35960834c819080eed0c9f32b881d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006ef0bc4c8190b06b03c06d344abf completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:16 a.m.