Triple

T6578604
Position Surface form Disambiguated ID Type / Status
Subject Droylsden E157234 entity
Predicate river P165 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: [Droylsden, river, River Medlock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Medlock
Context triple: [Droylsden, river, 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
    River Bain is a river in Lincolnshire, England, known for flowing through the town of Horncastle before joining the River Witham.
  • E. River Browney
    River Browney is a river in County Durham, England, that flows through former coal-mining areas before joining the River Wear near Durham.
  • 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_69c6882b3a108190b3a9eb343ae4162c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae8dad608190b4708368a7af6e5d completed March 27, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7616bf79481909b21f5e295a4d48a completed March 28, 2026, 5:04 a.m.
Created at: March 27, 2026, 1:54 p.m.