Triple

T13312486
Position Surface form Disambiguated ID Type / Status
Subject Volme E317103 entity
Predicate flowsThrough P225 FINISHED
Object Lüdenscheid E344748 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: Lüdenscheid | Statement: [Volme, flowsThrough, Lüdenscheid]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lüdenscheid
Context triple: [Volme, flowsThrough, Lüdenscheid]
  • A. Lüdenscheid chosen
    Lüdenscheid is a town in western Germany’s Sauerland region, historically noted for its role in World War II and known today for its metal and plastics industries.
  • B. Lüdinghausen
    Lüdinghausen is a historic town in western Germany known for its medieval castles and picturesque setting in the Münsterland region.
  • C. Burscheid
    Burscheid is a small town in North Rhine-Westphalia, Germany, known for its location in the hilly Bergisches Land region and its mix of rural character and local industry.
  • D. Schwelm
    Schwelm is a small town in North Rhine-Westphalia, Germany, known as the administrative seat of the Ennepe-Ruhr district.
  • E. Dülmen
    Dülmen is a town in western Germany’s North Rhine-Westphalia, known for its location between Münster and the Ruhr area and for the wild Dülmen ponies in the nearby nature reserve.
  • 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d990f6d34c8190ba19dc2df7d42c22 completed April 11, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69fee5da6a2081909dcc9785598e1196 completed May 9, 2026, 7:44 a.m.
Created at: April 9, 2026, 9:29 p.m.