Triple

T4267968
Position Surface form Disambiguated ID Type / Status
Subject historic county of Kent E96870 entity
Predicate contains P35 FINISHED
Object Ashford E46676 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: Ashford | Statement: [historic county of Kent, contains, Ashford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashford
Context triple: [historic county of Kent, contains, 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 a town in the borough of Spelthorne in Surrey, England, forming part of the London commuter belt.
  • D. New Ashford
    New Ashford is a small rural town in western Massachusetts, United States, known for its scenic setting in the Berkshires.
  • E. Bedford
    Bedford is a historic market town and the county town of Bedfordshire in eastern England, situated on the River Great Ouse.
  • 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_69b34543f06c8190915ebb1a4574ffa9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34fce710481909d90ed4a3d150fde completed March 12, 2026, 11:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5b79fe8c08190b4a9e4812babc78e completed March 14, 2026, 7:31 p.m.
Created at: March 12, 2026, 11:07 p.m.