Triple

T18005773
Position Surface form Disambiguated ID Type / Status
Subject Henmore Brook E430742 entity
Predicate flowsThrough P225 FINISHED
Object Ashbourne 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: Ashbourne | Statement: [Henmore Brook, flowsThrough, Ashbourne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashbourne
Context triple: [Henmore Brook, flowsThrough, Ashbourne]
  • A. Ashbourne chosen
    Ashbourne is a historic market town in Derbyshire, England, known for its traditional architecture and annual Royal Shrovetide Football match.
  • B. Ashbourne
    Ashbourne is a rapidly growing commuter town in County Meath, Ireland, located northwest of Dublin and known for its residential developments and local amenities.
  • C. Ashby
    Ashby is a small rural community located within the township of Addington Highlands in eastern Ontario, Canada.
  • D. Ashby
    Ashby is a surname most notably associated with Hal Ashby, the influential American film director known for 1970s classics such as "Harold and Maude" and "Being There."
  • E. Ashby
    Ashby is a small rural locality in the Clarence Valley region of New South Wales, Australia, known for its riverside setting and quiet village atmosphere.
  • 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b51ba1888190a339d726e92f376b completed April 19, 2026, 10:57 a.m.
Created at: April 10, 2026, 10:24 a.m.