Triple

T22055271
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Ancre (1916) E544991 entity
Predicate place P373 FINISHED
Object River Ancre 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 Ancre | Statement: [Battle of the Ancre (1916), place, River Ancre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Ancre
Context triple: [Battle of the Ancre (1916), place, River Ancre]
  • A. River Ancre chosen
    The River Ancre is a tributary of the Somme in northern France, known for flowing through key World War I battlefields on the Western Front.
  • B. River Ouse
    The River Ouse is a major river in East Sussex, England, flowing through towns such as Lewes before reaching the English Channel at Newhaven.
  • C. River Ouse
    River Ouse is a river in Tasmania, Australia, known for flowing through the central highlands and contributing to the region’s hydroelectric and agricultural systems.
  • D. River Ouse
    The River Ouse is a major river in North Yorkshire, England, flowing through the historic city of York and forming part of the Humber river system before reaching the North Sea.
  • E. Aire River
    Aire River is a watercourse in the canton of Geneva, Switzerland, known for flowing through rural landscapes and forming part of the local municipal boundaries.
  • 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_69e11e3377c48190890c17407b9527d6 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1285790948190b21abfb09abbb5e5 completed April 28, 2026, 9:36 p.m.
Created at: April 16, 2026, 8:26 p.m.