Triple

T6058868
Position Surface form Disambiguated ID Type / Status
Subject Epsom Common E134980 entity
Predicate near P350 FINISHED
Object Ashtead Common E379143 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: Ashtead Common | Statement: [Epsom Common, near, Ashtead Common]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashtead Common
Context triple: [Epsom Common, near, Ashtead Common]
  • A. Ashtead Common chosen
    Ashtead Common is a large ancient woodland and nature reserve in Surrey, England, known for its veteran oak trees and rich biodiversity.
  • B. 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.
  • C. 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.
  • D. Banstead Common
    Banstead Common is a large area of open common land in Banstead, Surrey, known for its heathland, woodland, and recreational walking and riding paths.
  • E. Hayes Common
    Hayes Common is a large area of heathland and woodland in the London Borough of Bromley, valued for recreation and nature conservation.
  • 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_69c00878d06881909ee78e88913bf890 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0570e64408190ae7a2504f63bb58a completed March 22, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c12520dfa4819080578766a070b98b completed March 23, 2026, 11:33 a.m.
Created at: March 22, 2026, 4:10 p.m.