Triple

T6855936
Position Surface form Disambiguated ID Type / Status
Subject Lymm Interchange E158142 entity
Predicate near P350 FINISHED
Object Lymm E34787 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: Lymm | Statement: [Lymm Interchange, near, Lymm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lymm
Context triple: [Lymm Interchange, near, Lymm]
  • A. Lymm chosen
    Lymm is a picturesque village in Cheshire, England, known for its historic center, scenic waterways, and surrounding countryside.
  • B. 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.
  • C. Sandbach
    Sandbach is a historic market town in Cheshire, England, noted for its Saxon crosses and traditional town centre.
  • D. Wyre
    Wyre is a district and local government area in Lancashire, England, named after the River Wyre and known for its mix of coastal towns and rural countryside.
  • E. Winsford
    Winsford is a town in Cheshire, England, known historically for its salt mining industry and its location along the River Weaver.
  • 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_69c6882fae988190864cbba788c5ebb4 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d86f03ac8190b4307156ab65a276 completed March 27, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72fe28dc88190a9c7794b78374ecf completed March 28, 2026, 1:33 a.m.
Created at: March 27, 2026, 2:20 p.m.