Triple

T7023479
Position Surface form Disambiguated ID Type / Status
Subject CH postcode area E162884 entity
Predicate servesTown P847 FINISHED
Object Neston E332858 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: Neston | Statement: [CH postcode area, servesTown, Neston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neston
Context triple: [CH postcode area, servesTown, Neston]
  • A. Neston chosen
    Neston is a small town on the Wirral Peninsula in Cheshire, England, known for its semi-rural character and proximity to both the River Dee and Liverpool.
  • B. Wells-next-the-Sea
    Wells-next-the-Sea is a small coastal town in Norfolk, England, known for its picturesque harbor, expansive sandy beach, and traditional seaside charm.
  • C. Seaham
    Seaham is a coastal town in North East England known for its seafront, historic harbor, and former coal mining heritage.
  • D. Seaham
    Seaham is a small rural town in the Hunter Region of New South Wales, Australia, known for its historic buildings and riverside setting.
  • E. Hornsea
    Hornsea is a small seaside town and former fishing village on the North Sea coast of the East Riding of Yorkshire in England, known for its beach, promenade, and nearby Hornsea Mere.
  • 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_69c6885b26248190a857541e3d10e299 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1edf3608190b7ba0bfb85710e97 completed March 27, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7757c87788190b09ced669b5c4d83 completed March 28, 2026, 6:30 a.m.
Created at: March 27, 2026, 2:35 p.m.