Triple

T20456632
Position Surface form Disambiguated ID Type / Status
Subject Erkrath E501804 entity
Predicate adjacentTo P224 FINISHED
Object Mettmann 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: Mettmann | Statement: [Erkrath, adjacentTo, Mettmann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mettmann
Context triple: [Erkrath, adjacentTo, Mettmann]
  • A. Mettmann chosen
    Mettmann is a town in western Germany’s North Rhine-Westphalia region, known as the administrative center of the Mettmann district and for its proximity to the Neander Valley.
  • 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. Meppen
    Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
  • D. Hennef
    Hennef is a town in North Rhine-Westphalia, Germany, situated on the river Sieg near Bonn and known for its mix of residential areas, industry, and surrounding countryside.
  • E. Euskirchen
    Euskirchen is a town in the German state of North Rhine-Westphalia, known as a regional center near Bonn and the Eifel region.
  • 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_69e0b4ad4940819098cf2ff6413574e5 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e696a1b03c8190984d9db6d3251308 completed April 20, 2026, 9:12 p.m.
Created at: April 16, 2026, 11:32 a.m.