Triple

T21195996
Position Surface form Disambiguated ID Type / Status
Subject Löhne–Rheine railway E522326 entity
Predicate connects P390 FINISHED
Object Bünde (Westfalen) 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: Bünde (Westfalen) | Statement: [Löhne–Rheine railway, connects, Bünde (Westfalen)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bünde (Westfalen)
Context triple: [Löhne–Rheine railway, connects, Bünde (Westfalen)]
  • A. Bünde chosen
    Bünde is a small town in the German state of North Rhine-Westphalia, known historically for its cigar industry and location in the Herford district.
  • B. Büren (Westphalia)
    Büren (Westphalia) is a small historic town in the Paderborn district of North Rhine-Westphalia, Germany, known for its rural setting and regional cultural heritage.
  • C. Nordhorn
    Nordhorn is a town in Lower Saxony, Germany, known as the administrative center of the Grafschaft Bentheim district near the Dutch border.
  • D. Meppen
    Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
  • E. Lüdinghausen
    Lüdinghausen is a historic town in western Germany known for its medieval castles and picturesque setting in the Münsterland region.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7333bd7a0819084bbd1d6c111bc65 completed April 21, 2026, 8:20 a.m.
Created at: April 16, 2026, 3:08 p.m.