Triple

T21277129
Position Surface form Disambiguated ID Type / Status
Subject Minden-Lübbecke district E524416 entity
Predicate contains P35 FINISHED
Object Rahden 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: Rahden | Statement: [Minden-Lübbecke district, contains, Rahden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rahden
Context triple: [Minden-Lübbecke district, contains, Rahden]
  • A. Rahden chosen
    Rahden is a small town in North Rhine-Westphalia, Germany, known for its rural character and traditional Westphalian heritage.
  • B. Rüthi
    Rüthi is a municipality in the canton of St. Gallen in northeastern Switzerland, located in the Rhine Valley near the border with Austria.
  • C. Hardegsen
    Hardegsen is a small town in Lower Saxony, Germany, known for its medieval castle and historic town center.
  • D. 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.
  • E. Radeberg
    Radeberg is a small town in the German state of Saxony, known for its Radeberger Pilsner brewery and historic town center near Dresden.
  • 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_69e0b516293c819089458ea2ec85f85e completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736583c08819087a4726538e703e2 completed April 21, 2026, 8:33 a.m.
Created at: April 16, 2026, 4:02 p.m.