Triple

T16424488
Position Surface form Disambiguated ID Type / Status
Subject Märkischer Kreis E398905 entity
Predicate hasMunicipality P847 FINISHED
Object Neuenrade E1077912 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: Neuenrade | Statement: [Märkischer Kreis, hasMunicipality, Neuenrade]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neuenrade
Context triple: [Märkischer Kreis, hasMunicipality, Neuenrade]
  • A. Neuenrade chosen
    Neuenrade is a small town in western Germany, located in the state of North Rhine-Westphalia and known for its scenic setting in the Sauerland region.
  • B. 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.
  • C. Nordhorn
    Nordhorn is a town in Lower Saxony, Germany, known as the administrative center of the Grafschaft Bentheim district near the Dutch border.
  • D. Rüdinghausen
    Rüdinghausen is a district of the city of Witten in North Rhine-Westphalia, Germany, characterized by its residential areas and local amenities.
  • E. Langenfeld
    Langenfeld is a town in western Germany, located in the state of North Rhine-Westphalia between Düsseldorf and Cologne.
  • 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_6a0179313470819090351e937ea34701 completed May 11, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:09 a.m.