Triple

T19556247
Position Surface form Disambiguated ID Type / Status
Subject River Trent at Keadby E489318 entity
Predicate adjacentTo P224 FINISHED
Object Keadby village NE NERFINISHED

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: Keadby village | Statement: [River Trent at Keadby, adjacentTo, Keadby village]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Keadby village
Context triple: [River Trent at Keadby, adjacentTo, Keadby village]
  • A. Keadby chosen
    Keadby is a village in North Lincolnshire, England, known for its location on the River Trent and its nearby power station and transport links.
  • B. Vickleby
    Vickleby is a small village on the island of Öland in southeastern Sweden, known for its traditional rural landscape and historic church.
  • C. Navenby
    Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
  • D. Vinstra village
    Vinstra village is a small settlement in Innlandet county, Norway, known as a local service and transport hub in the Gudbrandsdalen valley.
  • E. Hunsonby
    Hunsonby is a small rural village and civil parish in Cumbria, England, situated in the Eden Valley near the town of Penrith.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63d341d708190b8ef35822f8bfe7c completed April 20, 2026, 2:50 p.m.
Created at: April 10, 2026, 1:42 p.m.