Triple

T13030604
Position Surface form Disambiguated ID Type / Status
Subject Ashford District E326428 entity
Predicate hasSettlement P1068 FINISHED
Object Biddenden E546725 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: Biddenden | Statement: [Ashford District, hasSettlement, Biddenden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Biddenden
Context triple: [Ashford District, hasSettlement, Biddenden]
  • A. Biddenden chosen
    Biddenden is a historic village in Kent, England, known for its traditional Wealden architecture, vineyards, and the local legend of the Biddenden Maids.
  • B. Willingdon
    Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
  • C. Thrupp
    Thrupp is a small canal-side village in Oxfordshire, England, known for its historic wharf and picturesque setting along the Oxford Canal.
  • D. Tilbury
    Tilbury is a small community within the municipality of Chatham-Kent in southwestern Ontario, Canada, known for its agricultural surroundings and local services.
  • E. Tilbury
    Tilbury is a port town on the north bank of the River Thames in Essex, England, known for its docks and historic forts guarding the approach to 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_69d8076cc45c81908123123f43e69266 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97efd18308190877b3269403b36e2 completed April 10, 2026, 10:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6d5fa10fc81908a37b85894f8f849 completed May 3, 2026, 4:58 a.m.
Created at: April 9, 2026, 8:54 p.m.