Triple

T8438324
Position Surface form Disambiguated ID Type / Status
Subject Mechernich E199285 entity
Predicate locatedNear P294 FINISHED
Object Euskirchen E412673 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: Euskirchen | Statement: [Mechernich, locatedNear, Euskirchen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Euskirchen
Context triple: [Mechernich, locatedNear, Euskirchen]
  • A. Euskirchen chosen
    Euskirchen is a town in the German state of North Rhine-Westphalia, known as a regional center near Bonn and the Eifel region.
  • B. Remscheid
    Remscheid is a city in North Rhine-Westphalia, Germany, known historically for its metalworking industry and as the birthplace of physicist Wilhelm Röntgen.
  • C. Bergkamen
    Bergkamen is a town in North Rhine-Westphalia, Germany, known for its coal mining heritage and post-war planned urban development.
  • D. Herzogenrath
    Herzogenrath is a town in western Germany near the Dutch border, known for its cross-border cooperation with the neighboring Dutch town of Kerkrade.
  • E. Oberhausen
    Oberhausen is an industrial city in Germany’s Ruhr region, historically known for its coal and steel production and heavily affected by World War II bombing.
  • 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_69ca8314cd6c8190a6b8c2a1096e18f3 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe135657c81908ed8156fbfbef6ec completed March 31, 2026, 2:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0c696913c819089f29ec899d4ee61 completed April 4, 2026, 8:06 a.m.
Created at: March 30, 2026, 6:08 p.m.