Triple

T14557417
Position Surface form Disambiguated ID Type / Status
Subject Bromley Common and Keston ward E341577 entity
Predicate coversArea P175 FINISHED
Object Keston E48400 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: Keston | Statement: [Bromley Common and Keston ward, coversArea, Keston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Keston
Context triple: [Bromley Common and Keston ward, coversArea, Keston]
  • A. Keston chosen
    Keston is a historic village in the London Borough of Bromley, known for its rural character, commons, and proximity to the source of the River Ravensbourne.
  • B. Kerian
    Kerian is a given name used as a personal first name.
  • C. Heastie
    Heastie is the surname of Carl E. Heastie, a prominent American politician who has served as Speaker of the New York State Assembly.
  • D. Kushma
    Kushma is a small town in central Nepal known for its dramatic suspension bridges and role as the administrative center of Parbat District.
  • E. Kesten
    Kesten is a surname most notably associated with Harry Kesten, a prominent mathematician known for his work in probability theory.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2f1490881908673f429e5288c86 completed April 14, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8abde0308190819da6867e703ea7 completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:23 a.m.