Triple

T8293013
Position Surface form Disambiguated ID Type / Status
Subject East Suffolk district E193944 entity
Predicate contains P35 FINISHED
Object Martlesham E299701 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: Martlesham | Statement: [East Suffolk district, contains, Martlesham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Martlesham
Context triple: [East Suffolk district, contains, Martlesham]
  • A. Martlesham Heath chosen
    Martlesham Heath is a village and residential area in Suffolk, England, known for its planned development and historical links to aviation and telecommunications research.
  • B. Lyneham
    Lyneham is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
  • C. Shottisham
    Shottisham is a small rural village and civil parish in the English county of Suffolk, known for its traditional countryside character and historic church.
  • D. Kempshott
    Kempshott is a residential suburb of Basingstoke in Hampshire, England, known for its family housing and local amenities.
  • E. Paglesham
    Paglesham is a small rural village in Essex, England, known historically for its fishing, boatbuilding, and smuggling heritage along the River Roach.
  • 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_69ca82e32db481908b72f3804fa71152 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7c9deb50819086ae9c97b03fefc3 completed March 31, 2026, 7:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd952e038c819090023cbcdab1e3ae completed April 1, 2026, 9:59 p.m.
Created at: March 30, 2026, 5:52 p.m.