Triple

T12538964
Position Surface form Disambiguated ID Type / Status
Subject Assington E299784 entity
Predicate isNear P350 FINISHED
Object Leavenheath E299783 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: Leavenheath | Statement: [Assington, isNear, Leavenheath]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leavenheath
Context triple: [Assington, isNear, Leavenheath]
  • A. Leavenheath chosen
    Leavenheath is a village and civil parish on the border of Suffolk and Essex in eastern England, known for its rural setting near Dedham Vale and the Suffolk countryside.
  • B. Horningsheath
    Horningsheath is the former name of Horringer, a village in Suffolk, England, known for its historic rural character and proximity to Ickworth House.
  • C. Minstead
    Minstead is a small village in Hampshire, England, best known as the burial place of Sir Arthur Conan Doyle.
  • D. Thurne
    Thurne is a small village in Norfolk, England, known for its location within the Norfolk Broads and its iconic Thurne windpump.
  • E. Hawkenbury
    Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9546ebf508190ae54857e4289c6e4 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65eb10618819092540de09997a0c5 completed May 2, 2026, 8:29 p.m.
Created at: April 8, 2026, 9:57 p.m.