Triple

T1219562
Position Surface form Disambiguated ID Type / Status
Subject River Wey E26186 entity
Predicate passesSettlement P10456 FINISHED
Object Woking E22253 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: Woking | Statement: [River Wey, passesSettlement, Woking]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Woking
Context triple: [River Wey, passesSettlement, Woking]
  • A. Woking chosen
    Woking is a large commuter town in southeast England known for its rail links to London and its association with H.G. Wells’ "The War of the Worlds."
  • B. Basildon
    Basildon is a large town in Essex, England, known as a post-war new town and a major commercial and residential centre within the East of England.
  • C. Hounslow
    Hounslow is a suburban district in West London known for its diverse community, major transport links, and proximity to Heathrow Airport.
  • D. Bromley
    Bromley is a large suburban town in southeast London, England, known as a major commercial and retail centre within the London Borough of Bromley.
  • E. Dartford
    Dartford is a historic market and industrial town in southeast England, situated on the River Darent and serving as a key commuter hub for London.
  • 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf169868819090cfab7e34c40c67 completed March 1, 2026, 10:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad293648d08190a1c15fe677aa7b8c completed March 8, 2026, 7:45 a.m.
Created at: March 1, 2026, 7:46 p.m.