Triple

T3934544
Position Surface form Disambiguated ID Type / Status
Subject Battle of Warburg E90876 entity
Predicate near P350 FINISHED
Object River Diemel E255721 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 Diemel | Statement: [Battle of Warburg, near, River Diemel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Diemel
Context triple: [Battle of Warburg, near, River Diemel]
  • A. Diemel chosen
    The Diemel is a river in central Germany that flows through Hesse and North Rhine-Westphalia before joining the Weser.
  • B. Würm River
    The Würm River is a small river in Bavaria, Germany, known for flowing north from Lake Starnberg through towns such as Gauting and Starnberg before joining the Amper River.
  • C. Inn River
    The Inn River is a major Alpine river in Central Europe that flows through Switzerland, Austria, and Germany before joining the Danube.
  • D. River Pleiße
    The River Pleiße is a small river in central Germany that flows through the city and district of Leipzig, contributing to the region’s historic waterways and green corridors.
  • E. Regnitz
    The Regnitz is a river in the German state of Bavaria that flows through cities such as Erlangen and Bamberg before joining the Main River.
  • 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_69aed95f26e0819094b0e71974543a19 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeedcbf0188190a5e828707a77752a completed March 9, 2026, 3:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdf9f26be48190bf21b252a922ca69 completed March 21, 2026, 1:52 a.m.
Created at: March 9, 2026, 3:23 p.m.