Triple

T12191428
Position Surface form Disambiguated ID Type / Status
Subject Corvey E290471 entity
Predicate locatedOnRiver P165 FINISHED
Object Weser River E33257 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: Weser River | Statement: [Corvey, locatedOnRiver, Weser River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Weser River
Context triple: [Corvey, locatedOnRiver, Weser River]
  • A. Weser chosen
    The Weser is a major river in northwestern Germany that flows through several federal states before emptying into the North Sea.
  • B. Rheine
    Rheine is a German city in the state of North Rhine-Westphalia, known for its historical town center and location along the River Ems.
  • C. Rhine
    The Rhine is one of Europe's most important rivers, historically serving as a vital trade route and cultural boundary from the Alps through Germany to the North Sea.
  • D. Elbe
    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.
  • E. Blies
    The Blies is a river in western Germany and northeastern France that flows through the Saarland region before joining the Saar 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_69d6ab64de5881908d56eb7a75c6cc69 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91c5340248190b79379423f3a3ca1 completed April 10, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65e9a155c8190ad6c45dae0632c39 completed May 2, 2026, 8:29 p.m.
Created at: April 8, 2026, 9:50 p.m.