Triple

T16424491
Position Surface form Disambiguated ID Type / Status
Subject Märkischer Kreis E398905 entity
Predicate hasMunicipality P847 FINISHED
Object Werdohl NE ONNED1

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: Werdohl | Statement: [Märkischer Kreis, hasMunicipality, Werdohl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Werdohl
Context triple: [Märkischer Kreis, hasMunicipality, Werdohl]
  • A. Werdohl chosen
    Werdohl is a town in the Märkischer Kreis district of North Rhine-Westphalia, Germany, known for its metalworking industry and location in the hilly Sauerland region.
  • B. Gevelsberg
    Gevelsberg is a town in North Rhine-Westphalia, Germany, situated in the Ennepe-Ruhr district within the Ruhr metropolitan region.
  • C. Radevormwald
    Radevormwald is a small historic town in North Rhine-Westphalia, western Germany, known for its hilly Bergisches Land landscape and traditional textile and metalworking industries.
  • D. Gescher
    Gescher is a small town in western Germany’s Münsterland region, noted for its traditional bell foundries and rural character.
  • E. Waldbröl
    Waldbröl is a small town in North Rhine-Westphalia, Germany, known for its rural setting in the Bergisches Land region.
  • 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_69d87f2b9024819085c20e52de95d583 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328f9da9081908dadbdac4b2d38ec completed April 18, 2026, 6:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01953eaa6c819091f7d63a1e3e7070 in_progress May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:09 a.m.