Triple

T22123268
Position Surface form Disambiguated ID Type / Status
Subject Biddenden E546725 entity
Predicate nearbyTown P3883 FINISHED
Object Ashford 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: Ashford | Statement: [Biddenden, nearbyTown, Ashford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashford
Context triple: [Biddenden, nearbyTown, Ashford]
  • A. Ashford chosen
    Ashford is a large and rapidly growing town in the county of Kent in southeast England, known as a key transport hub with high-speed rail links to London and continental Europe.
  • B. Ashford
    Ashford is a small rural town in northern New South Wales, Australia, known for agriculture and its proximity to natural attractions such as caves and rivers.
  • C. Ashford
    Ashford is an inner south-western suburb of Adelaide, South Australia, known for its proximity to the city centre and major medical facilities.
  • D. Ashford
    Ashford is a town in the Reach, a fertile and populous region of the continent of Westeros in the world of "A Song of Ice and Fire."
  • E. Ashford
    Ashford is an English-language surname of Old English origin, commonly associated with various notable individuals and several towns in England.
  • 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_69e11e39bf348190b541bfa16a7b71e0 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1297f3fb48190b6aaca18b40c37ab completed April 28, 2026, 9:41 p.m.
Created at: April 16, 2026, 8:31 p.m.