Triple

T16405339
Position Surface form Disambiguated ID Type / Status
Subject Waverley, Surrey E398410 entity
Predicate containsSettlement P847 FINISHED
Object Frensham E518866 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: Frensham | Statement: [Waverley, Surrey, containsSettlement, Frensham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frensham
Context triple: [Waverley, Surrey, 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. Nether Wallop
    Nether Wallop is a small historic village in Hampshire, England, known for its picturesque rural character and traditional thatched cottages.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d2b4e48190b7153f198639e9cd completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a003c62614c8190acd6d211cab1be11 completed May 10, 2026, 8:05 a.m.
Created at: April 10, 2026, 5:09 a.m.