Triple

T22084373
Position Surface form Disambiguated ID Type / Status
Subject Southeast Kent E545734 entity
Predicate contains P35 FINISHED
Object Hythe 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: Hythe | Statement: [Southeast Kent, contains, Hythe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hythe
Context triple: [Southeast Kent, contains, Hythe]
  • A. Hythe chosen
    Hythe is a historic coastal town in Kent, England, known as one of the original Cinque Ports that once played a key role in maritime defense and trade.
  • B. Hythe
    Hythe is a small village in northwestern Alberta, Canada, situated west of the city of Grande Prairie.
  • C. Hythe
    Hythe is a coastal village and port town in Hampshire, England, situated on the edge of Southampton Water and known for its historic pier and ferry link to Southampton.
  • D. Hythe Bay
    Hythe Bay is a coastal area along the English Channel in Kent, England, known for its shingle beach, seaside views, and proximity to towns such as Sandgate and Hythe.
  • E. Wyke
    Wyke is a village and suburb in the metropolitan borough of Bradford, West Yorkshire, England.
  • 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_69e11e3523488190badd54b5d580c00d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f128b95e908190bd846f531eb59b50 completed April 28, 2026, 9:38 p.m.
Created at: April 16, 2026, 8:29 p.m.