Triple

T23509722
Position Surface form Disambiguated ID Type / Status
Subject River Tone E572381 entity
Predicate hasTributary P415 FINISHED
Object Sherford Stream 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: Sherford Stream | Statement: [River Tone, hasTributary, Sherford Stream]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sherford Stream
Context triple: [River Tone, hasTributary, Sherford Stream]
  • A. Sherford Stream chosen
    Sherford Stream is a small watercourse in Somerset, England, that serves as a minor tributary feeding into the River Tone within its local drainage network.
  • B. Longford Stream
    Longford Stream is a small watercourse in East Sussex, England, that forms part of the River Ouse drainage system.
  • C. Sutherland Stream
    Sutherland Stream is a watercourse in Saskatchewan, Canada, that serves as an outlet for Quill Lake within the region’s local drainage system.
  • D. Hinksey Stream
    Hinksey Stream is a minor watercourse in Oxford, England, that branches from and rejoins the River Thames, flowing through the Hinksey area and contributing to the local river network and floodplain.
  • E. Cavenham Stream
    Cavenham Stream is a small watercourse in Suffolk, England, that serves as a minor tributary within the River Lark catchment.
  • 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_69e245b5e4208190bac8a6509867e394 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a90455f0819092b37c69d7e73c43 completed April 29, 2026, 6:45 a.m.
Created at: April 17, 2026, 6:07 p.m.