Triple

T9840409
Position Surface form Disambiguated ID Type / Status
Subject Keston Ponds E239207 entity
Predicate near P350 FINISHED
Object Hayes Common E88468 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: Hayes Common | Statement: [Keston Ponds, near, Hayes Common]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hayes Common
Context triple: [Keston Ponds, near, Hayes Common]
  • A. Hayes Common chosen
    Hayes Common is a large area of heathland and woodland in the London Borough of Bromley, valued for recreation and nature conservation.
  • B. Peppard Common
    Peppard Common is a village and civil parish in South Oxfordshire, England, known for its rural character and proximity to the Chiltern Hills.
  • C. Hungerford Common
    Hungerford Common is a large open area of common land near the town of Hungerford in Berkshire, England, known for its grazing, walking paths, and wildlife.
  • D. Keston Common
    Keston Common is a large area of heathland and woodland in the London Borough of Bromley, valued for its natural habitats, walking paths, and local wildlife.
  • E. Barnes Common
    Barnes Common is a large area of public open woodland and grassland in Barnes, southwest London, known for its natural habitats and recreational space.
  • 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_69ca84e3f0c48190ada72a65ebd50efd completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb34b045481908f89abd576aab497 completed April 2, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1e429682c8190a94339b96d4081f6 completed April 5, 2026, 4:25 a.m.
Created at: March 30, 2026, 8:33 p.m.