Triple

T13277864
Position Surface form Disambiguated ID Type / Status
Subject Norfolk Coast Path E316238 entity
Predicate passesThrough P225 FINISHED
Object Mundesley E290204 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: Mundesley | Statement: [Norfolk Coast Path, passesThrough, Mundesley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mundesley
Context triple: [Norfolk Coast Path, passesThrough, Mundesley]
  • A. Mundesley chosen
    Mundesley is a coastal village and seaside resort on the North Sea in Norfolk, England, known for its sandy beaches and traditional holiday atmosphere.
  • B. Caistor
    Caistor is a small historic market town in Lincolnshire, England, known for its Roman origins and Georgian architecture.
  • C. Mendlesham
    Mendlesham is a rural village and civil parish in Suffolk, England, known for its historic church and traditional village character.
  • D. Worstead
    Worstead is a small rural village and railway stop in Norfolk, England, situated on the Bittern Line between Norwich and the North Norfolk coast.
  • E. Monkseaton
    Monkseaton is a suburban area in North Tyneside, England, known primarily as a residential community with its own Metro station and local amenities.
  • 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_69d806b349908190a9a61dd9323bf153 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99043fba88190872ede6f63e2fbcb completed April 11, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69f70a54ff488190a759b46963c0d842 completed May 3, 2026, 8:41 a.m.
Created at: April 9, 2026, 9:26 p.m.