Triple

T7843701
Position Surface form Disambiguated ID Type / Status
Subject River Coquet E181866 entity
Predicate flowsThrough P225 FINISHED
Object Hepple E679394 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: Hepple | Statement: [River Coquet, flowsThrough, Hepple]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hepple
Context triple: [River Coquet, flowsThrough, Hepple]
  • A. Hepple chosen
    Hepple is a small rural village in Northumberland, England, situated in the scenic Coquet Valley.
  • B. Brighouse
    Brighouse is a market and industrial town in the metropolitan borough of Calderdale in northern England.
  • C. Slaithwaite
    Slaithwaite is a village in West Yorkshire, England, situated in the Colne Valley near Huddersfield and known for its historic canalside setting and former textile mills.
  • D. Milnrow
    Milnrow is a town in Greater Manchester, England, historically part of Lancashire and known for its textile heritage and proximity to the Pennine hills.
  • E. Ferryhill
    Ferryhill is a small town in County Durham, England, known historically for its coal mining heritage and location between Durham and Darlington.
  • 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_69ca8285d6488190a95d4c02d7354b53 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb163c72248190b53bc53980e8ac0f completed March 31, 2026, 12:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5ae9758c819091e270343ed289aa completed March 31, 2026, 5:26 a.m.
Created at: March 30, 2026, 4:48 p.m.