Triple

T19183721
Position Surface form Disambiguated ID Type / Status
Subject Norham Bridge E469642 entity
Predicate locatedIn P40 FINISHED
Object Norham NE NERFINISHED

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: Norham | Statement: [Norham Bridge, locatedIn, Norham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Norham
Context triple: [Norham Bridge, locatedIn, Norham]
  • A. Norham chosen
    Norham is a historic village in Northumberland, England, known for its medieval castle overlooking the River Tweed near the Scottish border.
  • B. Ranworth
    Ranworth is a small village in Norfolk, England, known for its scenic setting within the Norfolk Broads and its historic parish church.
  • C. Framlingham
    Framlingham is a historic market town in Suffolk, England, best known for its well-preserved medieval castle.
  • D. Bamburgh
    Bamburgh is a historic coastal village in Northumberland, England, best known for its imposing medieval castle overlooking the North Sea.
  • E. Hawkenbury
    Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dd0ad9088190a173b32657ae2e7a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f61e1c248190ba9e220c1be61ef8 completed April 20, 2026, 9:47 a.m.
Created at: April 10, 2026, 12:07 p.m.