Triple

T8596139
Position Surface form Disambiguated ID Type / Status
Subject Chertsey Bridge E203550 entity
Predicate connects P390 FINISHED
Object Shepperton E34847 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: Shepperton | Statement: [Chertsey Bridge, connects, Shepperton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shepperton
Context triple: [Chertsey Bridge, connects, Shepperton]
  • A. Shepperton chosen
    Shepperton is a suburban town in Surrey, England, known for its film studios and riverside location on the River Thames.
  • B. 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.
  • C. Tadworth
    Tadworth is a suburban village in Surrey, England, situated on the North Downs and known for its residential character and proximity to Epsom Downs.
  • D. Sunbury-on-Thames
    Sunbury-on-Thames is a suburban town on the River Thames in south-east England, historically part of Middlesex and now within the borough of Spelthorne.
  • E. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • 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_69ca832a7f108190b4e4f5648abf4aa2 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46c945dc8190a313c61c0db46187 completed March 31, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea8d3fcfc8190bc51a38715ed453e completed April 2, 2026, 5:35 p.m.
Created at: March 30, 2026, 6:23 p.m.