Triple

T6603428
Position Surface form Disambiguated ID Type / Status
Subject Littlehampton E149057 entity
Predicate hasSuburb P747 FINISHED
Object Rustington E187224 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: Rustington | Statement: [Littlehampton, hasSuburb, Rustington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rustington
Context triple: [Littlehampton, hasSuburb, Rustington]
  • A. Rustington chosen
    Rustington is a large coastal village and civil parish on the English Channel in the Arun District of West Sussex, England.
  • B. Billingshurst
    Billingshurst is a large village and civil parish in the Horsham District of West Sussex, England, known for its historic High Street and role as a local residential and commercial centre.
  • C. Hassocks
    Hassocks is a large village and civil parish in the Mid Sussex district of West Sussex, England, situated just north of the South Downs and known for its commuter links to Brighton and London.
  • D. Haslemere
    Haslemere is a historic market town in the southwest of Surrey, England, near the borders with Hampshire and West Sussex.
  • E. Ruskington
    Ruskington is a large village and civil parish in Lincolnshire, England, known for its rural character and position near the River Slea.
  • 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_69c687eaa7508190bb58ce2aa02039b3 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6af11f0788190be010c6ee60e150c completed March 27, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c748926b6c819080a2d32759529dae completed March 28, 2026, 3:18 a.m.
Created at: March 27, 2026, 1:56 p.m.