Triple

T18247337
Position Surface form Disambiguated ID Type / Status
Subject Tilford E436986 entity
Predicate near P350 FINISHED
Object Farnham 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: Farnham | Statement: [Tilford, near, Farnham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Farnham
Context triple: [Tilford, near, Farnham]
  • A. Farnham chosen
    Farnham is a historic market town in southern England known for its Georgian streets, medieval castle, and surrounding Surrey countryside.
  • B. Camberley
    Camberley is a suburban town in southeast England known for its shopping centre, commuter links to London, and proximity to the Royal Military Academy Sandhurst.
  • C. Guildford
    Guildford is a historic suburb of Perth in Western Australia, known as one of the state’s earliest settlements and a gateway to the Swan Valley wine region.
  • D. Guildford
    Guildford is a historic market town in southeast England known for its medieval architecture, university, and role as a commercial and cultural hub in the region.
  • E. Wokingham
    Wokingham is a historic market town in Berkshire, England, known for its traditional town center and role as a commuter hub for nearby Reading and London.
  • 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_69d8b91104e08190a8241f7d260a5162 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4f7e89b288190a286797ec2cd60a8 completed April 19, 2026, 3:42 p.m.
Created at: April 10, 2026, 10:33 a.m.