Triple

T22566861
Position Surface form Disambiguated ID Type / Status
Subject Weser River valley E557973 entity
Predicate containsSettlement P847 FINISHED
Object Rinteln NE NERFINISHED

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: Rinteln | Statement: [Weser River valley, containsSettlement, Rinteln]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rinteln
Context triple: [Weser River valley, containsSettlement, Rinteln]
  • A. Rinteln chosen
    Rinteln is a historic town in Lower Saxony, Germany, situated on the River Weser and known for its well-preserved medieval architecture.
  • B. Radeberg
    Radeberg is a small town in the German state of Saxony, known for its Radeberger Pilsner brewery and historic town center near Dresden.
  • C. Radeburg
    Radeburg is a small town in the German state of Saxony, situated north of Dresden and known for its historic center and surrounding rural landscape.
  • D. Retzow
    Retzow is a small municipality in the Havelland district of the federal state of Brandenburg in northeastern Germany.
  • E. Rheinhausen
    Rheinhausen is a district of the German city of Duisburg, located on the western bank of the Rhine in North Rhine-Westphalia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e5ae4ac8190b1f503457603d969 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15faaa0b081908d5aa8f3ba1e3dd3 completed April 29, 2026, 1:32 a.m.
Created at: April 16, 2026, 8:52 p.m.