Triple

T17690649
Position Surface form Disambiguated ID Type / Status
Subject Ashingdon E441016 entity
Predicate near P350 FINISHED
Object Rochford NE NERFINISHED

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: Rochford | Statement: [Ashingdon, near, Rochford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rochford
Context triple: [Ashingdon, near, Rochford]
  • A. Rochford chosen
    Rochford is a small town in Essex, England, serving as the administrative center for the surrounding Rochford District.
  • B. Rochford hundred
    Rochford hundred was a historic administrative division in Essex, England, centered around the town of Rochford and used for local governance and judicial purposes.
  • C. Rochford District
    Rochford District is a local government district in Essex, England, encompassing both rural communities and parts of the Southend urban area, including London Southend Airport.
  • D. Rainford
    Rainford is a village and civil parish in Merseyside, England, known for its semi-rural character and historical links to agriculture and light industry.
  • E. Fordwich
    Fordwich is a small historic town in Kent, England, often noted as one of the smallest towns in Britain and situated near Canterbury.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9e940b081908b862bb0e6e89b0d completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4704b43a88190ba29654ca695839e completed April 19, 2026, 6:03 a.m.
Created at: April 10, 2026, 10:03 a.m.