Triple

T2608350
Position Surface form Disambiguated ID Type / Status
Subject River Evenlode E58714 entity
Predicate flowsThrough P225 FINISHED
Object Long Hanborough E92501 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: Long Hanborough | Statement: [River Evenlode, flowsThrough, Long Hanborough]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Long Hanborough
Context triple: [River Evenlode, flowsThrough, Long Hanborough]
  • A. Long Hanborough chosen
    Long Hanborough is a rural village in Oxfordshire, England, known for its proximity to Blenheim Palace and its railway links to Oxford and London.
  • B. Longridge
    Longridge is a small village located in the council area of West Lothian in central Scotland.
  • C. Longridge
    Longridge is a small town in Lancashire, England, known for its historic stone quarrying industry and scenic location on the edge of the Ribble Valley.
  • D. Wideford Hill
    Wideford Hill is a prominent hill on Mainland, Orkney, known for its panoramic views and nearby prehistoric archaeological sites.
  • E. Gadebridge
    Gadebridge is a residential area and suburb of Hemel Hempstead in Hertfordshire, England.
  • 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_69ab4ac3523881909679750c9f8c2dec completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd86769b88190935151a01c1ac855 completed March 7, 2026, 7:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69af83e1efb88190b79c2c6ac0e87647 completed March 10, 2026, 2:37 a.m.
Created at: March 6, 2026, 9:49 p.m.