Triple

T13585694
Position Surface form Disambiguated ID Type / Status
Subject Little Glemham E324552 entity
Predicate near P350 FINISHED
Object Saxmundham E309042 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: Saxmundham | Statement: [Little Glemham, near, Saxmundham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saxmundham
Context triple: [Little Glemham, near, Saxmundham]
  • A. Saxmundham chosen
    Saxmundham is a small market town in the English county of Suffolk, known as a local commercial and transport hub for the surrounding rural area.
  • B. Cheshunt
    Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
  • C. Shenfield
    Shenfield is a suburban town in Essex, England, known as a key commuter hub with a major railway station connecting to London.
  • D. Orsett
    Orsett is a village and civil parish in the borough of Thurrock in Essex, England, known for its historic church and traditional village green.
  • E. Saffron Walden
    Saffron Walden is a historic market town in Essex, England, known for its well-preserved medieval architecture and former saffron trade.
  • 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_69d80769100c819099111274614f5ed2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb03310fc819092a56b9f2d73f560 completed April 12, 2026, 2:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f8deae88190b932a57789c70e77 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:49 p.m.