Triple

T12033046
Position Surface form Disambiguated ID Type / Status
Subject A217 road E286459 entity
Predicate connects P390 FINISHED
Object Reigate E22887 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: Reigate | Statement: [A217 road, connects, Reigate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reigate
Context triple: [A217 road, connects, Reigate]
  • A. Reigate chosen
    Reigate is a historic market town in southeast England, situated at the foot of the North Downs and known for its castle ruins, caves, and commuter links to London.
  • B. Beddington
    Beddington is a suburban area in South London known for its historic village core, green spaces, and proximity to Croydon and central London.
  • 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. 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.
  • 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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9040724ec8190808f334013ddc6d6 completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcdee6798c8190b2b47082cf0c32fb completed May 7, 2026, 6:50 p.m.
Created at: April 8, 2026, 9:47 p.m.