Triple

T6367527
Position Surface form Disambiguated ID Type / Status
Subject Angmering E143263 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object East Preston E547647 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: East Preston | Statement: [Angmering, hasNeighbouringSettlement, East Preston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: East Preston
Context triple: [Angmering, hasNeighbouringSettlement, East Preston]
  • A. East Preston chosen
    East Preston is a coastal village in West Sussex, England, situated within the Arun District and known for its residential character and seaside location.
  • B. Preston
    Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
  • C. Preston
    Preston is a historic industrial city in Lancashire, England, known for its role in the Industrial Revolution and its status as a major urban center in the North West.
  • D. Preston
    Preston is a masculine given name of English origin that has been used both as a first name and a surname.
  • E. Croston
    Croston is a historic village in Lancashire, England, known for its picturesque rural setting, traditional architecture, and riverside location.
  • 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_69c008d8c61081908bcaf61510d881ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c068251ae48190af8201d5f9ad35b6 completed March 22, 2026, 10:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c62d8689408190b334928df870ed29 completed March 27, 2026, 7:11 a.m.
Created at: March 22, 2026, 4:32 p.m.