Triple

T4778171
Position Surface form Disambiguated ID Type / Status
Subject Lowton E106104 entity
Predicate locatedNear P294 FINISHED
Object Leigh E59813 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: Leigh | Statement: [Lowton, locatedNear, Leigh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leigh
Context triple: [Lowton, locatedNear, Leigh]
  • A. Leigh
    Leigh is a given name and surname of English origin, used for all genders and often considered a variant spelling of "Lee."
  • B. Leigh chosen
    Leigh is a parliamentary constituency in Greater Manchester, England, historically represented in the UK House of Commons.
  • C. Birkenhead
    Birkenhead is a town in north west England, situated on the Wirral Peninsula across the River Mersey from Liverpool, known historically for its shipbuilding and docks.
  • D. Bauple
    Bauple is a small rural town in Queensland, Australia, known as the birthplace of the macadamia nut and situated within the Fraser Coast Region.
  • E. Leyland
    Leyland is a town in Lancashire, England, historically known for its vehicle manufacturing industry, particularly Leyland Motors.
  • 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_69bd43f3074c8190937e7b0a457fe9f1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd658942e481908570cfec77fe4a4b completed March 20, 2026, 3:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69be4d912f5c81909537b861dd0a4591 completed March 21, 2026, 7:49 a.m.
Created at: March 20, 2026, 1:21 p.m.