Triple

T2934490
Position Surface form Disambiguated ID Type / Status
Subject West Byfleet E79232 entity
Predicate nearbySettlement P350 FINISHED
Object Pyrford E79488 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: Pyrford | Statement: [West Byfleet, nearbySettlement, Pyrford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pyrford
Context triple: [West Byfleet, nearbySettlement, Pyrford]
  • A. Pyrford chosen
    Pyrford is a village in Surrey, England, known for its historic church, green spaces, and residential character near the town of Woking.
  • B. Twyford
    Twyford is a village and civil parish in Berkshire, England, known as a commuter settlement between Reading and London.
  • C. Petersham
    Petersham is a historic riverside village in southwest London, known for its green spaces, period architecture, and location between Richmond and Kingston along the River Thames.
  • D. Ruxley
    Ruxley is a locality in the London Borough of Bromley, England, known for its mix of suburban development and nearby nature reserves such as the Ruxley Gravel Pits.
  • E. Speldhurst
    Speldhurst is a rural village and civil parish in Kent, England, known for its historic church, traditional pubs, and scenic countryside near Royal Tunbridge Wells.
  • 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_69ad8b0fbab081908f6a61567c045d8d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad983c84688190aa7ed5b8091fb140 completed March 8, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69b0867ba1b48190a54d00c32b075548 completed March 10, 2026, 9 p.m.
Created at: March 8, 2026, 2:56 p.m.