Triple

T3042809
Position Surface form Disambiguated ID Type / Status
Subject Hythe E83169 entity
Predicate locatedNear P294 FINISHED
Object Folkestone E213999 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: Folkestone | Statement: [Hythe, locatedNear, Folkestone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Folkestone
Context triple: [Hythe, locatedNear, Folkestone]
  • A. Folkestone chosen
    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.
  • B. Folkestone and Hythe
    Folkestone and Hythe is a UK parliamentary constituency in Kent that covers the coastal towns of Folkestone and Hythe and their surrounding areas.
  • C. Ramsgate
    Ramsgate is a seaside town and port on the Isle of Thanet in Kent, England, known historically as a popular resort and maritime hub.
  • D. Eastbourne
    Eastbourne is a seaside town and popular coastal resort on England’s south coast, known for its Victorian architecture, long promenade, and proximity to the chalk cliffs of Beachy Head.
  • E. Fareham
    Fareham is a market town in southern England situated between the cities of Southampton and Portsmouth.
  • 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_69ad8b2298908190a7cb4e9bdbf064d0 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9b5d2a308190b4ce20efcae9b761 completed March 8, 2026, 3:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b1eef43da8819094cd438c93c64c86 completed March 11, 2026, 10:38 p.m.
Created at: March 8, 2026, 3:01 p.m.