Triple

T1219557
Position Surface form Disambiguated ID Type / Status
Subject River Wey E26186 entity
Predicate hasTributary P415 FINISHED
Object River Slea E159418 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 Slea | Statement: [River Wey, hasTributary, River Slea]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Slea
Context triple: [River Wey, hasTributary, River Slea]
  • A. River Slea chosen
    The River Slea is a small river in Lincolnshire, England, flowing through the town of Sleaford before joining the River Witham.
  • B. River Croal
    River Croal is a small river in Greater Manchester, England, that flows through Bolton before joining the River Irwell.
  • C. River Spodden
    River Spodden is a river in Lancashire and Greater Manchester, England, flowing through the South Pennines and the town of Bacup before joining the River Roch.
  • D. River Tawe
    The River Tawe is a river in South Wales that flows from the Brecon Beacons through Swansea to the Bristol Channel, historically supporting coal mining and industry along its valley.
  • E. River Plym
    River Plym is a river in Devon, England, that flows through Dartmoor and into Plymouth Sound, giving its name to the city of Plymouth.
  • 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be1d55a08190a138b2411a7c4376 completed March 1, 2026, 10:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69ace55382c88190b838478f3c178c2d completed March 8, 2026, 2:56 a.m.
Created at: March 1, 2026, 7:46 p.m.