Triple

T21556956
Position Surface form Disambiguated ID Type / Status
Subject Ennepe E531916 entity
Predicate flowsThrough P225 FINISHED
Object Breckerfeld 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: Breckerfeld | Statement: [Ennepe, flowsThrough, Breckerfeld]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Breckerfeld
Context triple: [Ennepe, flowsThrough, Breckerfeld]
  • A. Breckerfeld chosen
    Breckerfeld is a small town in North Rhine-Westphalia, Germany, known for its rural character and location in the hilly, forested region of the Sauerland.
  • B. Ochtrup
    Ochtrup is a small town in the Münster region of North Rhine-Westphalia in western Germany, known for its textile industry and designer outlet center.
  • C. Dierdorf
    Dierdorf is a surname most prominently associated with former American football player and sportscaster Dan Dierdorf.
  • D. Gevelsberg
    Gevelsberg is a town in North Rhine-Westphalia, Germany, situated in the Ennepe-Ruhr district within the Ruhr metropolitan region.
  • E. Augustdorf
    Augustdorf is a municipality in North Rhine-Westphalia, Germany, known for its proximity to the Teutoburg Forest and its significant military presence, including Bundeswehr facilities.
  • 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2e04b048190ac3a9913094b4625 completed April 27, 2026, 3:07 a.m.
Created at: April 16, 2026, 6:29 p.m.