Triple

T15046313
Position Surface form Disambiguated ID Type / Status
Subject Burtonwood E379233 entity
Predicate near P350 FINISHED
Object Great Sankey E98562 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: Great Sankey | Statement: [Burtonwood, near, Great Sankey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Great Sankey
Context triple: [Burtonwood, near, Great Sankey]
  • A. Great Sankey chosen
    Great Sankey is a residential suburb and civil parish on the western side of Warrington in Cheshire, England.
  • B. Sankey Brook
    Sankey Brook is a watercourse in North West England that forms part of the River Mersey catchment and flows through the St Helens and Warrington area.
  • C. River Sankey
    River Sankey is a watercourse in North West England that flows through areas such as St Helens and Warrington before joining the River Mersey.
  • D. Taz River
    The Taz River is a major river in northwestern Siberia, Russia, that flows through the tundra of the Yamalo-Nenets region before emptying into the Kara Sea in the Arctic Ocean.
  • E. Jubilee River
    The Jubilee River is a man-made flood relief channel in Berkshire, England, designed to reduce flooding risk along the River Thames, particularly around Maidenhead, Windsor, and Eton.
  • 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_69d85cd64d108190853797a95c11cc45 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded830c3c08190a87b81abbbb75377 completed April 15, 2026, 12:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe9de73614819098b7a88624407d0e completed May 9, 2026, 2:37 a.m.
Created at: April 10, 2026, 3 a.m.