Triple

T18198674
Position Surface form Disambiguated ID Type / Status
Subject River Worth E435725 entity
Predicate flowsThrough P225 FINISHED
Object Oakworth 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: Oakworth | Statement: [River Worth, flowsThrough, Oakworth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oakworth
Context triple: [River Worth, flowsThrough, Oakworth]
  • A. Oakworth chosen
    Oakworth is a village in West Yorkshire, England, known for its rural setting and historic association with the Keighley and Worth Valley Railway.
  • B. Ackworth
    Ackworth is a village and civil parish in West Yorkshire, England, known for its historic buildings and rural character within the metropolitan borough of the City of Wakefield.
  • C. Cullingworth
    Cullingworth is a village in West Yorkshire, England, situated near the town of Bingley and within commuting distance of Bradford.
  • D. Worle
    Worle is a suburban area near Weston-super-Mare in North Somerset, England, known primarily as a residential community with rail links to surrounding regions.
  • E. Wetherby
    Wetherby is a market town in West Yorkshire, England, situated on the River Wharfe and known historically as a key coaching stop between London and Edinburgh.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d545f4819090285d1446bd3c27 completed April 19, 2026, 2:04 p.m.
Created at: April 10, 2026, 10:31 a.m.