Triple

T21000985
Position Surface form Disambiguated ID Type / Status
Subject Waverley District E517284 entity
Predicate containsSettlement P847 FINISHED
Object Frensham NE NERFINISHED

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: Frensham | Statement: [Waverley District, containsSettlement, Frensham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frensham
Context triple: [Waverley District, containsSettlement, Frensham]
  • A. Frensham chosen
    Frensham is a rural village in Surrey, England, known for its scenic commons, ponds, and surrounding countryside.
  • B. Windlesham
    Windlesham is a village and civil parish in the Surrey Heath district of Surrey, England, known for its affluent residential character and leafy surroundings.
  • C. Wrecclesham
    Wrecclesham is a village and suburb on the outskirts of Farnham in Surrey, England, known for its residential character and local community amenities.
  • D. Horsham
    Horsham is a regional city in western Victoria, Australia, serving as a key commercial and service hub for the Wimmera region.
  • E. Frensham Common
    Frensham Common is a large heathland and nature reserve in Surrey, England, known for its sandy terrain, wildlife habitats, and popular walking and recreation areas.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5006e2881909fc2383f841740cc completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc25c1f8819086bdbfd89d390f5f completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:52 p.m.