Triple

T17788680
Position Surface form Disambiguated ID Type / Status
Subject Bellingham E444091 entity
Predicate near P350 FINISHED
Object Downham NE NERFINISHED

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: Downham | Statement: [Bellingham, near, Downham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Downham
Context triple: [Bellingham, near, Downham]
  • A. Downham chosen
    Downham is a picturesque rural village in Lancashire, England, known for its unspoiled traditional character and scenic setting near Pendle Hill.
  • B. Downham
    Downham is a residential district in southeast London known for its interwar housing estates and suburban character within the London Borough of Lewisham.
  • C. Harwich
    Harwich is a historic port town in Essex, England, which once served as a parliamentary borough represented in the British House of Commons.
  • D. Harwich
    Harwich is a coastal town on southeastern Cape Cod in Massachusetts known for its beaches, harbors, and summer tourism.
  • E. Lowestoft
    Lowestoft is a coastal town in Suffolk, England, known as the easternmost settlement in the United Kingdom and a traditional fishing and seaside resort.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9ef17708190bdf7e2adbf14ddc2 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4879524bc819090855ab5248c73db completed April 19, 2026, 7:43 a.m.
Created at: April 10, 2026, 10:12 a.m.