Triple

T13505687
Position Surface form Disambiguated ID Type / Status
Subject Folkestone and Hythe District E321009 entity
Predicate contains P35 FINISHED
Object Lyminge E927661 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: Lyminge | Statement: [Folkestone and Hythe District, contains, Lyminge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lyminge
Context triple: [Folkestone and Hythe District, contains, Lyminge]
  • A. Lyminge chosen
    Lyminge is a historic village in Kent, England, notable for its early medieval Anglo-Saxon archaeological remains and religious significance.
  • B. Hensingham
    Hensingham is a residential suburb of Whitehaven in Cumbria, England, known for its local community facilities and proximity to the town’s centre.
  • C. Waldringfield
    Waldringfield is a small riverside village in eastern England known for its scenic setting on the River Deben and sailing activities.
  • D. Hellingly
    Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
  • E. Minstead
    Minstead is a small village in Hampshire, England, best known as the burial place of Sir Arthur Conan Doyle.
  • 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_69d807629d6c8190998f1b9bb12d2ed0 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaf8259a08190ada13c4a3078f07d completed April 12, 2026, 2:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7548bc188819090773db66b0103a1 completed May 3, 2026, 1:58 p.m.
Created at: April 9, 2026, 9:43 p.m.