Triple

T7369126
Position Surface form Disambiguated ID Type / Status
Subject Shippea Hill railway station E169948 entity
Predicate locatedNear P294 FINISHED
Object Littleport E166174 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: Littleport | Statement: [Shippea Hill railway station, locatedNear, Littleport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Littleport
Context triple: [Shippea Hill railway station, locatedNear, Littleport]
  • A. Littleport chosen
    Littleport is a large village and civil parish in East Cambridgeshire, England, situated near the River Great Ouse north of the city of Ely.
  • B. Milborne Port
    Milborne Port was a former parliamentary borough in Somerset, England, that historically returned members to the House of Commons.
  • C. Winterton
    Winterton is a small town in North Lincolnshire, England, known for its historic roots and rural character.
  • D. East Stour
    East Stour is a smaller river in Kent, England, that forms part of the River Stour’s drainage system.
  • E. Bridport
    Bridport is a historic market town in southwest England known for its rope-making heritage and proximity to the Jurassic Coast.
  • 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_69c68a5ade988190885b7175f63b7534 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1810668819094aec4b237d08068 completed March 27, 2026, 9:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802bfaa10819083ab3137dbdeefb6 completed March 28, 2026, 4:33 p.m.
Created at: March 27, 2026, 3:07 p.m.