Triple

T13656760
Position Surface form Disambiguated ID Type / Status
Subject New Addington E326880 entity
Predicate locatedNear P294 FINISHED
Object Addington E326880 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: Addington | Statement: [New Addington, locatedNear, Addington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Addington
Context triple: [New Addington, locatedNear, Addington]
  • A. Addington chosen
    Addington is a village in the London Borough of Croydon, historically part of Surrey, known for its rural character and association with several 19th-century Archbishops of Canterbury.
  • B. Addington
    Addington is a small village in Kent, England, known for its rural character and historic buildings.
  • C. Addington Hills
    Addington Hills is a large area of heathland and woodland in the London Borough of Croydon, known for its walking trails and panoramic views over London.
  • D. Addington Highlands
    Addington Highlands is a rural township in eastern Ontario, Canada, known for its lakes, forests, and outdoor recreation areas.
  • E. Boughton
    Boughton is a small rural village in Norfolk, England, situated near the settlement of Stoke Ferry.
  • 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc61d56e4819084ae3c16ecdf4a05 completed April 12, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f79d46c48c81908d64f1a32cf08c5b completed May 3, 2026, 7:08 p.m.
Created at: April 9, 2026, 9:52 p.m.