Triple

T11623230
Position Surface form Disambiguated ID Type / Status
Subject Blaubeuren E276192 entity
Predicate locatedOnWaterbody P1489 FINISHED
Object Blau River E211308 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: Blau River | Statement: [Blaubeuren, locatedOnWaterbody, Blau River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Blau River
Context triple: [Blaubeuren, locatedOnWaterbody, Blau River]
  • A. Blau River chosen
    The Blau River is a small river in the state of Baden-Württemberg in southern Germany, known for flowing through the Swabian Jura and joining the Danube at Ulm.
  • B. Rednitz River
    The Rednitz River is a river in Franconia, Germany, that flows through cities such as Fürth before joining the Pegnitz to form the Regnitz.
  • C. Lauch River
    The Lauch River is a small waterway in northeastern France that flows through the historic city of Colmar, contributing to its picturesque canals and “Little Venice” district.
  • D. Fuhse River
    The Fuhse River is a tributary waterway in northern Germany that flows through Lower Saxony before joining the Aller River.
  • E. Uecker River
    The Uecker River is a waterway in northeastern Germany that flows through the Uckermark region before emptying into the Szczecin Lagoon.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a122a3708190ab6513dad4c4fde7 completed April 10, 2026, 7:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69f63ed82a548190ab9326daef78e30b completed May 2, 2026, 6:13 p.m.
Created at: April 8, 2026, 9:39 p.m.