Triple

T19187231
Position Surface form Disambiguated ID Type / Status
Subject Lowton Common E469732 entity
Predicate locatedNear P294 FINISHED
Object Newton-le-Willows 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: Newton-le-Willows | Statement: [Lowton Common, locatedNear, Newton-le-Willows]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newton-le-Willows
Context triple: [Lowton Common, locatedNear, Newton-le-Willows]
  • A. Newton-le-Willows chosen
    Newton-le-Willows is a market town in northwestern England known for its historic role in early railway development and its location between Liverpool and Manchester.
  • B. Heswall
    Heswall is a town on the Wirral Peninsula in Merseyside, England, known for its residential character, golf courses, and views over the Dee Estuary toward North Wales.
  • C. Levenshulme
    Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
  • D. Liverpool Wavertree
    Liverpool Wavertree is a UK parliamentary constituency in the city of Liverpool, represented in the House of Commons.
  • E. Leylands
    Leylands is a residential neighbourhood within the town of Burgess Hill in West Sussex, 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_69e5f620f1f08190a0daaf0d1483d724 completed April 20, 2026, 9:47 a.m.
Created at: April 10, 2026, 12:07 p.m.