Triple

T678099
Position Surface form Disambiguated ID Type / Status
Subject Nuremberg E13122 entity
Predicate nearRiver P350 FINISHED
Object Regnitz River E100723 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: Regnitz River | Statement: [Nuremberg, nearRiver, Regnitz River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Regnitz River
Context triple: [Nuremberg, nearRiver, Regnitz River]
  • A. Neckar
    The Neckar is a significant river in southwestern Germany that flows through cities like Stuttgart and Heidelberg before joining the Rhine.
  • B. Pegnitz River chosen
    The Pegnitz River is a river in the German state of Bavaria that flows through the city of Nuremberg and joins the Rednitz to form the Regnitz.
  • C. Lahn
    The Lahn is a river in western Germany that flows through the states of North Rhine-Westphalia, Hesse, and Rhineland-Palatinate before joining the Rhine.
  • 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. Chemnitz River
    The Chemnitz River is a waterway in the German state of Saxony that flows through and gives its name to the city of Chemnitz.
  • 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_69a4933d3bf88190972041cd8cf143b9 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a04c89148190b6330e86697bb37b completed March 1, 2026, 8:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7a3a6bcf88190aff5bd3db264f475 completed March 4, 2026, 3:14 a.m.
Created at: March 1, 2026, 7:36 p.m.