Triple

T14063617
Position Surface form Disambiguated ID Type / Status
Subject East Raynham E338405 entity
Predicate hasPostTown P2711 FINISHED
Object Fakenham E11874 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: Fakenham | Statement: [East Raynham, hasPostTown, Fakenham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fakenham
Context triple: [East Raynham, hasPostTown, Fakenham]
  • A. Fakenham chosen
    Fakenham is a market town in Norfolk, England, known historically for its agriculture and as a local commercial center.
  • B. Swaffham
    Swaffham is a historic market town in the English county of Norfolk, known for its traditional town center and surrounding rural landscape.
  • C. Fakenham Magna
    Fakenham Magna is a small rural village and civil parish located in the county of Suffolk in eastern England.
  • D. Wroxham
    Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
  • E. Swaffham Bulbeck
    Swaffham Bulbeck is a rural village and civil parish in Cambridgeshire, England, known for its historic church, traditional architecture, and agricultural surroundings.
  • 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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5689c7f48190a47ca94eaa8a9ef9 completed April 14, 2026, 3 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb6673de881909653c7691422b800 completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:21 p.m.