Triple

T15366060
Position Surface form Disambiguated ID Type / Status
Subject Lees E367416 entity
Predicate locatedNear P294 FINISHED
Object River Medlock E14193 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: River Medlock | Statement: [Lees, locatedNear, River Medlock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Medlock
Context triple: [Lees, locatedNear, River Medlock]
  • A. River Medlock chosen
    The River Medlock is a small river in Greater Manchester, England, that flows through central Manchester and has played a significant role in the city’s industrial and urban development.
  • B. River Whiteadder
    River Whiteadder is a river in southeastern Scotland that flows through the Scottish Borders and East Lothian before joining the River Tweed.
  • C. River Brock
    River Brock is a small river in Lancashire, England, known for flowing through the Forest of Bowland before joining the River Wyre.
  • D. River Bain
    The River Bain is a small river in North Yorkshire, England, known for flowing from Semerwater to join the River Ure near Bainbridge.
  • E. River Bain
    River Bain is a river in Lincolnshire, England, known for flowing through the town of Horncastle before joining the River Witham.
  • 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_69d85a1483788190ad93c2748e8af34b completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e497de48190be249b110999ec5c completed April 16, 2026, 1:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff2cec4f2481908fae5209bfd48dcf completed May 9, 2026, 12:47 p.m.
Created at: April 10, 2026, 3:18 a.m.