Triple

T9208568
Position Surface form Disambiguated ID Type / Status
Subject Letcombe Bassett E221050 entity
Predicate locatedOn P40 FINISHED
Object Letcombe Brook E242486 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: Letcombe Brook | Statement: [Letcombe Bassett, locatedOn, Letcombe Brook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Letcombe Brook
Context triple: [Letcombe Bassett, locatedOn, Letcombe Brook]
  • A. Letcombe Brook chosen
    Letcombe Brook is a small chalk stream in Oxfordshire, England, valued for its clear waters, rich wildlife, and role in the local landscape around Wantage.
  • B. Henmore Brook
    Henmore Brook is a small watercourse in Derbyshire, England, that flows through the town of Ashbourne before joining the River Dove.
  • C. Shuttleworth Brook
    Shuttleworth Brook is a small watercourse in Lancashire, England, that serves as a minor tributary within the River Calder catchment.
  • D. Heathcote Brook
    Heathcote Brook is a small stream in central New Jersey that feeds into the Millstone River as part of the Raritan River watershed.
  • E. Ockley Brook
    Ockley Brook is a small watercourse in Oxfordshire, England, that feeds into the River Cherwell as part of the local river network.
  • 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_69ca83e9d0e081908bdb71097201a06c completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd9b217008190a0ab4971dd4a8899 completed April 1, 2026, 8:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69d228318de881909bbf4e68331bb586 completed April 5, 2026, 9:15 a.m.
Created at: March 30, 2026, 7:26 p.m.