Triple

T23062087
Position Surface form Disambiguated ID Type / Status
Subject Louth E574931 entity
Predicate locatedOnRiver P165 FINISHED
Object River Lud NE NERFINISHED

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 Lud | Statement: [Louth, locatedOnRiver, River Lud]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Lud
Context triple: [Louth, locatedOnRiver, River Lud]
  • A. River Lud chosen
    The River Lud is a small river in Lincolnshire, England, that flows through the market town of Louth before joining the River Witham system.
  • B. River Lyde
    The River Lyde is a small river in Hampshire, England, that flows through rural landscapes before joining the River Loddon.
  • C. Lez River
    The Lez River is a short coastal river in southern France that flows through the city of Montpellier before emptying into the Mediterranean Sea.
  • D. River Thur
    River Thur is a major river in northeastern Switzerland that flows through the canton of Thurgau before joining the Rhine.
  • 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 (2 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_69e245bd6e4c8190bb8942245b68cad5 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f189a0c3c881909f137ad511c216ac completed April 29, 2026, 4:31 a.m.
Created at: April 17, 2026, 3:55 p.m.