Triple

T11520951
Position Surface form Disambiguated ID Type / Status
Subject Leamington Spa E273158 entity
Predicate hasRiver P165 FINISHED
Object River Leam E664584 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 Leam | Statement: [Leamington Spa, hasRiver, River Leam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Leam
Context triple: [Leamington Spa, hasRiver, River Leam]
  • A. River Leam chosen
    The River Leam is a small river in central England that flows through the town of Leamington Spa before joining the River Avon.
  • B. River Lyde
    The River Lyde is a small river in Hampshire, England, that flows through rural landscapes before joining the River Loddon.
  • C. 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.
  • D. River Stort
    The River Stort is a tributary river in southern England that flows through Hertfordshire and Essex, joining the River Lea near the town of Hoddesdon.
  • E. River Soar
    The River Soar is a major river in central England that flows through Leicestershire and the city of Leicester before joining the River Trent.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d87fd129c88190893b95222480e04a completed April 10, 2026, 4:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ef822a90e48190874a87bd9a634685 completed April 27, 2026, 3:35 p.m.
Created at: April 8, 2026, 9:36 p.m.