Triple

T21557063
Position Surface form Disambiguated ID Type / Status
Subject Halver E531919 entity
Predicate locatedNear P294 FINISHED
Object Schalksmühle 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: Schalksmühle | Statement: [Halver, locatedNear, Schalksmühle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schalksmühle
Context triple: [Halver, locatedNear, Schalksmühle]
  • A. Schalksmühle chosen
    Schalksmühle is a small municipality in the Märkischer Kreis district of North Rhine-Westphalia, Germany, known for its location in the hilly Sauerland region and its electrical and metalworking industries.
  • B. Gevelsberg
    Gevelsberg is a town in North Rhine-Westphalia, Germany, situated in the Ennepe-Ruhr district within the Ruhr metropolitan region.
  • C. Gescher
    Gescher is a small town in western Germany’s Münsterland region, noted for its traditional bell foundries and rural character.
  • D. Wedemark
    Wedemark is a municipality in Lower Saxony, Germany, located north of Hanover and known for its semi-rural character and commuter links to the city.
  • E. Rudolfswerth
    Rudolfswerth is the former German name for Novo Mesto, a historic town in southeastern Slovenia known for its medieval heritage and role as a regional cultural center.
  • 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.