Triple

T17832705
Position Surface form Disambiguated ID Type / Status
Subject Norfolk E445301 entity
Predicate hasMajorTown P316 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: [Norfolk, hasMajorTown, Fakenham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fakenham
Context triple: [Norfolk, hasMajorTown, 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_69d8b9f1a6d881909f024bc603111cdb completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48d257414819088730f48ad7ab9ae completed April 19, 2026, 8:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0313b707048190847024da11394ed3 completed May 12, 2026, 11:49 a.m.
Created at: April 10, 2026, 10:15 a.m.