Triple

T5239298
Position Surface form Disambiguated ID Type / Status
Subject River Hull E118299 entity
Predicate flowsThrough P225 FINISHED
Object Beverley E406105 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: Beverley | Statement: [River Hull, flowsThrough, Beverley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beverley
Context triple: [River Hull, flowsThrough, Beverley]
  • A. Beverley chosen
    Beverley is a historic market town and civil parish in the East Riding of Yorkshire, England, known for its impressive Gothic minster and medieval architecture.
  • B. Yorkton
    Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
  • C. Bakewell
    Bakewell is a historic market town in Derbyshire, England, famed for its traditional Bakewell pudding and its picturesque setting in the Peak District.
  • D. Northbourne
    Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • E. Brough
    Brough is a village and civil parish in the East Riding of Yorkshire, England, situated on the northern bank of the Humber Estuary.
  • 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_69bd4467db0881909b3b0982df32cc8f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b290b88819095bc99c234260d25 completed March 20, 2026, 4:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef823afd88190a3a41e7fff09d449 completed March 21, 2026, 7:57 p.m.
Created at: March 20, 2026, 1:49 p.m.