Triple

T7027879
Position Surface form Disambiguated ID Type / Status
Subject Battle of Medway E163193 entity
Predicate location P40 FINISHED
Object River Medway E38818 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 Medway | Statement: [Battle of Medway, location, River Medway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Medway
Context triple: [Battle of Medway, location, River Medway]
  • A. River Medway chosen
    The River Medway is a major river in South East England that flows through Kent and Sussex, historically important for navigation, trade, and the development of towns such as Maidstone and Rochester.
  • B. River Brent
    The River Brent is a tributary of the River Thames in West London, flowing through several London boroughs and giving its name to the London Borough of Brent.
  • C. River Wick
    River Wick is a small river in northern Scotland that flows through the town of Wick before entering the North Sea.
  • D. River Dean
    River Dean is a small river in Cheshire, England, that flows through the town of Bollington and the surrounding countryside.
  • E. 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.
  • 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_69c6885d691c81908cf7d31083113886 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1fee32081908eff988b18daa6d0 completed March 27, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ad743c2c819081d7b8cda5720ba3 completed March 28, 2026, 10:29 a.m.
Created at: March 27, 2026, 2:35 p.m.