Triple

T14724694
Position Surface form Disambiguated ID Type / Status
Subject Woburn E345907 entity
Predicate near P350 FINISHED
Object Dunstable E194625 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: Dunstable | Statement: [Woburn, near, Dunstable]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dunstable
Context triple: [Woburn, near, Dunstable]
  • A. Dunstable chosen
    Dunstable is a historic market town in Bedfordshire, England, known for its location at the crossroads of ancient routes and its proximity to the Chiltern Hills.
  • B. Abingdon
    Abingdon is a historic market town in Oxfordshire, England, often claimed to be one of the oldest continuously inhabited towns in the country.
  • C. Hunsdon
    Hunsdon is a rural village and civil parish in Hertfordshire, England, known for its historic airfield and countryside setting.
  • D. Biddenden
    Biddenden is a historic village in Kent, England, known for its traditional Wealden architecture, vineyards, and the local legend of the Biddenden Maids.
  • E. Berkhamsted
    Berkhamsted is a historic market town in Hertfordshire, England, known for its medieval castle remains and role as a commuter hub northwest of 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec25e9a14819081fa06fc601f295d completed April 14, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf09791e081908a1262717fd31445 completed May 8, 2026, 2:17 p.m.
Created at: April 10, 2026, 1:29 a.m.