Triple

T3224301
Position Surface form Disambiguated ID Type / Status
Subject Tonbridge and Malling Borough E67586 entity
Predicate contains P35 FINISHED
Object Aylesford E201614 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: Aylesford | Statement: [Tonbridge and Malling Borough, contains, Aylesford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aylesford
Context triple: [Tonbridge and Malling Borough, contains, Aylesford]
  • A. Aylesford chosen
    Aylesford is a historic village in Kent, England, known for its ancient bridge, riverside setting, and archaeological significance.
  • B. Eynsford
    Eynsford is a historic village in the Sevenoaks District of Kent, England, known for its medieval castle ruins and picturesque rural setting.
  • C. Faversham
    Faversham is a historic market town in Kent, England, known for its medieval architecture, maritime heritage, and long-standing brewing industry.
  • D. Fairford
    Fairford is a small market town in Gloucestershire, England, known for its historic wool church and proximity to RAF Fairford airbase.
  • E. Uckfield
    Uckfield is a small market town in East Sussex, England, known for its historic high street and role as a local commercial and commuter hub.
  • 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_69ad858b8adc8190ad989712c87a476b completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adae1ae8f08190880d0f0e8539cdbc completed March 8, 2026, 5:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69b2625a22148190927b2a63ae3fc726 completed March 12, 2026, 6:51 a.m.
Created at: March 8, 2026, 3:08 p.m.