Triple

T1308635
Position Surface form Disambiguated ID Type / Status
Subject Runnymede Borough E27937 entity
Predicate contains P35 FINISHED
Object Addlestone E28020 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: Addlestone | Statement: [Runnymede Borough, contains, Addlestone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Addlestone
Context triple: [Runnymede Borough, contains, Addlestone]
  • A. Addlestone chosen
    Addlestone is a suburban town in southeast England known for its residential character and proximity to London.
  • B. Banstead
    Banstead is a suburban town in southeast England known for its village-like high street and green spaces within the county of Surrey.
  • C. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • D. Wallington
    Wallington is a suburban town in the London Borough of Sutton, known for its residential character, grammar schools, and green spaces in south London, England.
  • E. Esher
    Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to 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_69a496d7d83481908f83085854e51328 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c13806b48190a0db33f8e5d53734 completed March 1, 2026, 10:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69af903825d881909c3f2ec2c307019d completed March 10, 2026, 3:30 a.m.
Created at: March 1, 2026, 7:51 p.m.