Triple

T13697803
Position Surface form Disambiguated ID Type / Status
Subject Kent Estuary E328432 entity
Predicate mouthOf P1008 FINISHED
Object River Kent E82861 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 Kent | Statement: [Kent Estuary, mouthOf, River Kent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Kent
Context triple: [Kent Estuary, mouthOf, River Kent]
  • A. River Kent chosen
    The River Kent is a river in Cumbria, England, that flows through the town of Kendal before emptying into the estuarine waters of Morecambe Bay.
  • B. River Kinder
    The River Kinder is a small moorland river in the Peak District of England, known for its dramatic Kinder Downfall waterfall and rugged upland scenery.
  • C. River Brit
    The River Brit is a small river in West Dorset, England, that flows through the town of Bridport before reaching the English Channel at West Bay.
  • D. River Brun
    River Brun is a small river in Lancashire, England, that flows through the town of Burnley and contributes to its local landscape and waterways.
  • E. Taz River
    The Taz River is a major river in northwestern Siberia, Russia, that flows through the tundra of the Yamalo-Nenets region before emptying into the Kara Sea in the Arctic Ocean.
  • 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_69d8076ff62081908a7bd79889edd7a0 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc878b57c819094e7ea6d1a64211f completed April 12, 2026, 4:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf7cfcf748190944ffea7582d4f66 completed May 7, 2026, 8:36 p.m.
Created at: April 9, 2026, 9:54 p.m.