Triple

T13676604
Position Surface form Disambiguated ID Type / Status
Subject Pevensey E327893 entity
Predicate near P350 FINISHED
Object Eastbourne E62189 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: Eastbourne | Statement: [Pevensey, near, Eastbourne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eastbourne
Context triple: [Pevensey, near, Eastbourne]
  • A. Eastbourne chosen
    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.
  • B. Bexhill-on-Sea
    Bexhill-on-Sea is a seaside town in East Sussex, England, known for its Victorian and Edwardian architecture and the modernist De La Warr Pavilion on the south coast.
  • C. 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.
  • D. Bexhill and Battle
    Bexhill and Battle is a UK parliamentary constituency in East Sussex, represented in the House of Commons and centered on the towns of Bexhill-on-Sea and Battle.
  • E. Worthing
    Worthing is a large seaside town and resort on the south coast of England in West Sussex.
  • 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_69d8076f1fa8819094664a59b55010df completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc65c04988190b675e6fb7241e53c completed April 12, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd466ac0f08190b99dd4cdcef339c6 completed May 8, 2026, 2:11 a.m.
Created at: April 9, 2026, 9:53 p.m.