Triple

T7611207
Position Surface form Disambiguated ID Type / Status
Subject CT postcode area E172239 entity
Predicate hasPostTown P2711 FINISHED
Object Whitstable E498251 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: Whitstable | Statement: [CT postcode area, hasPostTown, Whitstable]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Whitstable
Context triple: [CT postcode area, hasPostTown, Whitstable]
  • A. Whitstable chosen
    Whitstable is a coastal town on the north coast of Kent in southeast England, known for its historic oyster fishing industry and pebble beaches.
  • B. Folkestone
    Folkestone is a coastal town and port in Kent, England, known as a gateway to continental Europe via the Channel Tunnel and nearby ferry links.
  • C. Brightlingsea
    Brightlingsea is a coastal town in Essex, England, historically known for its maritime trade, shipbuilding, and association with the medieval Cinque Ports confederation.
  • D. Hildenborough
    Hildenborough is a village in Kent, England, situated near Tonbridge and known for its commuter links to London and surrounding towns.
  • E. Richborough
    Richborough is a historic site in Kent, England, known for its significant Roman remains and its role as a key gateway to Roman Britain.
  • 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_69c6994f50808190ba228764bb422417 completed March 27, 2026, 2:50 p.m.
NER Named-entity recognition batch_69c6fa221c848190b892ba1caec8d83a completed March 27, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8e575c22481908a6779f5d496bd3a completed March 29, 2026, 8:40 a.m.
Created at: March 27, 2026, 3:55 p.m.