Triple

T14694401
Position Surface form Disambiguated ID Type / Status
Subject Blohm & Voss shipyard, Hamburg E345115 entity
Predicate locatedOn P40 FINISHED
Object River Elbe E16410 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 Elbe | Statement: [Blohm & Voss shipyard, Hamburg, locatedOn, River Elbe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Elbe
Context triple: [Blohm & Voss shipyard, Hamburg, locatedOn, River Elbe]
  • A. Elbe chosen
    The Elbe is one of Central Europe's major rivers, flowing from the Czech Republic through Germany to the North Sea and serving as an important waterway for transport, industry, and agriculture.
  • B. Saale
    The Saale is a major river in central Germany that flows through the states of Thuringia, Saxony-Anhalt, and Bavaria before joining the Elbe.
  • C. Weser
    The Weser is a major river in northwestern Germany that flows through several federal states before emptying into the North Sea.
  • D. 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.
  • E. Elbe basin
    The Elbe basin is the extensive drainage area of the Elbe River in Central Europe, encompassing parts of Germany, the Czech Republic, and neighboring regions.
  • 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_69d822e34b348190ada4d1cdb6c7c226 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb586e7108190be644db9cf9a4d99 completed April 14, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe64ec72bc819085fa2c21487f297e completed May 8, 2026, 10:34 p.m.
Created at: April 10, 2026, 1:28 a.m.