Triple

T6302986
Position Surface form Disambiguated ID Type / Status
Subject Petworth E141299 entity
Predicate hasRiver P165 FINISHED
Object River Rother E408943 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 Rother | Statement: [Petworth, hasRiver, River Rother]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Rother
Context triple: [Petworth, hasRiver, River Rother]
  • A. River Rother
    The River Rother is a river in central England that flows through Derbyshire and South Yorkshire before joining the River Don.
  • B. River Rother chosen
    River Rother is a river in East Sussex, England, that flows through the Weald to the English Channel near the town of Rye.
  • C. River Adur
    The River Adur is a river in West Sussex, England, that flows through the South Downs to reach the English Channel at Shoreham-by-Sea.
  • D. River Darent
    River Darent is a chalk stream river in Kent, England, flowing north through the Darent Valley to join the River Thames.
  • E. River Kennet
    River Kennet is a significant chalk stream in southern England that flows through Wiltshire and Berkshire before joining the River Thames.
  • 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645e150881908b49a07914dcbfd8 completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7580ad55081908bb7c70fca29cb22 completed March 28, 2026, 4:24 a.m.
Created at: March 22, 2026, 4:27 p.m.