Triple

T12036375
Position Surface form Disambiguated ID Type / Status
Subject Solingen E286549 entity
Predicate locatedNear P294 FINISHED
Object Remscheid E272299 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: Remscheid | Statement: [Solingen, locatedNear, Remscheid]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Remscheid
Context triple: [Solingen, locatedNear, Remscheid]
  • A. Remscheid chosen
    Remscheid is a city in North Rhine-Westphalia, Germany, known historically for its metalworking industry and as the birthplace of physicist Wilhelm Röntgen.
  • B. Bergkamen
    Bergkamen is a town in North Rhine-Westphalia, Germany, known for its coal mining heritage and post-war planned urban development.
  • C. Recklinghausen
    Recklinghausen is a city in the Ruhr area of North Rhine-Westphalia, western Germany, known historically for coal mining and its role as a regional administrative center.
  • D. Gelsenkirchen
    Gelsenkirchen is a city in western Germany known for its strong football culture and modern stadium, Veltins-Arena, home to FC Schalke 04.
  • 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 (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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90408cbf0819093270c9833ef149a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8b788308190bd9c3b68569bc56a completed May 3, 2026, 2:53 a.m.
Created at: April 8, 2026, 9:47 p.m.