Triple

T6687088
Position Surface form Disambiguated ID Type / Status
Subject Longcross E152124 entity
Predicate locatedNear P294 FINISHED
Object Windlesham E27354 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: Windlesham | Statement: [Longcross, locatedNear, Windlesham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Windlesham
Context triple: [Longcross, locatedNear, Windlesham]
  • A. Windlesham chosen
    Windlesham is a village and civil parish in the Surrey Heath district of Surrey, England, known for its affluent residential character and leafy surroundings.
  • B. Frensham
    Frensham is a rural village in Surrey, England, known for its scenic commons, ponds, and surrounding countryside.
  • C. Clisham
    Clisham is the highest mountain on the Isle of Harris in Scotland’s Outer Hebrides, known for its rugged terrain and panoramic coastal views.
  • D. Minstead
    Minstead is a small village in Hampshire, England, best known as the burial place of Sir Arthur Conan Doyle.
  • E. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • 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_69c687f9977c819097e7f5ada4fe522e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b14e58708190a4ba8ff1c085f160 completed March 27, 2026, 4:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6f7b0c0148190a232ed10950ec92b completed March 27, 2026, 9:33 p.m.
Created at: March 27, 2026, 2:04 p.m.