Triple

T22160470
Position Surface form Disambiguated ID Type / Status
Subject Littlehampton Beach E547652 entity
Predicate nearby P350 FINISHED
Object Littlehampton town centre 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: Littlehampton town centre | Statement: [Littlehampton Beach, nearby, Littlehampton town centre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Littlehampton town centre
Context triple: [Littlehampton Beach, nearby, Littlehampton town centre]
  • A. Littlehampton chosen
    Littlehampton is a seaside town and port on the south coast of England, known for its beaches, marina, and position at the mouth of the River Arun.
  • B. Shoreham-by-Sea
    Shoreham-by-Sea is a coastal town in South East England known for its historic harbour, beaches, and position at the mouth of the River Adur.
  • C. Haslemere
    Haslemere is a historic market town in the southwest of Surrey, England, near the borders with Hampshire and West Sussex.
  • D. Hanham
    Hanham is a suburban village and residential area on the eastern edge of Bristol in South West England.
  • E. Bognor Regis and Littlehampton
    Bognor Regis and Littlehampton is a UK parliamentary constituency in West Sussex that elects a Member of Parliament to the House of Commons.
  • 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_69e11e3c4c5c81908d336165816b12e0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a2c17a4819082fb9e4aaa275462 completed April 28, 2026, 9:44 p.m.
Created at: April 16, 2026, 8:33 p.m.