Triple

T3750345
Position Surface form Disambiguated ID Type / Status
Subject A243 road E81313 entity
Predicate connects P390 FINISHED
Object Chessington E213588 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: Chessington | Statement: [A243 road, connects, Chessington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chessington
Context triple: [A243 road, connects, Chessington]
  • A. Chessington chosen
    Chessington is a suburban area in the Royal Borough of Kingston upon Thames in southwest London, known for the Chessington World of Adventures Resort theme park and zoo.
  • B. Chobham
    Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
  • C. Isleworth
    Isleworth is a suburban town in West London, England, known for hosting major media and broadcasting facilities.
  • D. Chertsey
    Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
  • E. Datchet
    Datchet is a riverside village and civil parish in Berkshire, England, situated on the River Thames near Windsor.
  • 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_69ad8b19b7b08190a6188804e99c53e9 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcb6d0ac4819092c9a41cc60f518d completed March 8, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4db34aa5c8190ba3f22ee0f1f4208 completed March 14, 2026, 3:51 a.m.
Created at: March 8, 2026, 3:35 p.m.