Triple

T10379825
Position Surface form Disambiguated ID Type / Status
Subject Werse E244607 entity
Predicate flowsThrough P225 FINISHED
Object Drensteinfurt E210296 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: Drensteinfurt | Statement: [Werse, flowsThrough, Drensteinfurt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Drensteinfurt
Context triple: [Werse, flowsThrough, Drensteinfurt]
  • A. Drensteinfurt chosen
    Drensteinfurt is a small town in North Rhine-Westphalia, Germany, known for its historic architecture and location in the Münsterland region.
  • B. Adendorf
    Adendorf is a village-sized district within the municipality of Wachtberg in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
  • C. Dornstadt
    Dornstadt is a municipality in the Alb-Donau district of Baden-Württemberg in southern Germany, located near the city of Ulm.
  • D. Geiersthal
    Geiersthal is a small municipality in the Bavarian Forest region of southeastern Germany.
  • E. Kunreuth
    Kunreuth is a small municipality in the Upper Franconia region of Bavaria, Germany, known for its rural character and historic castle.
  • 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_69d381b3e328819094b23b8edcd29b5a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e991056c8190a981f717c51f1f72 completed April 7, 2026, 11:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69ef1243b14081909d07ab0ebb32cc68 completed April 27, 2026, 7:37 a.m.
Created at: April 6, 2026, 12:03 p.m.