Triple

T15809376
Position Surface form Disambiguated ID Type / Status
Subject Chelmsford E383304 entity
Predicate locatedOnRiver P165 FINISHED
Object River Chelmer E299057 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: River Chelmer | Statement: [Chelmsford, locatedOnRiver, River Chelmer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Chelmer
Context triple: [Chelmsford, locatedOnRiver, River Chelmer]
  • A. River Chelmer chosen
    The River Chelmer is a river in Essex, England, that flows through the city of Chelmsford before joining the River Blackwater near Maldon.
  • B. River Darent
    River Darent is a chalk stream river in Kent, England, flowing north through the Darent Valley to join the River Thames.
  • C. River Hamble
    The River Hamble is a river in Hampshire, England, renowned as a major yachting and boating centre and for its scenic, wooded estuary.
  • D. Great Stour
    The Great Stour is a major river in Kent, England, flowing through towns such as Ashford and Canterbury before reaching the English Channel.
  • E. River Wey
    The River Wey is a tributary of the River Thames in southern England, flowing through Hampshire and Surrey and historically important for navigation and trade.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b529c6b481909664153ecc381f7c completed April 16, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbbff15c81909cb148a33b51a16e completed May 10, 2026, 1:13 a.m.
Created at: April 10, 2026, 4:48 a.m.