Triple

T20456631
Position Surface form Disambiguated ID Type / Status
Subject Erkrath E501804 entity
Predicate adjacentTo P224 FINISHED
Object Hilden 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: Hilden | Statement: [Erkrath, adjacentTo, Hilden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hilden
Context triple: [Erkrath, adjacentTo, Hilden]
  • A. Hilden chosen
    Hilden is a town in western Germany’s North Rhine-Westphalia region, known for its proximity to Düsseldorf and its mix of residential, commercial, and light industrial areas.
  • B. Holten
    Holten is a village in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
  • C. Hamminkeln
    Hamminkeln is a small town and municipality in western Germany’s North Rhine-Westphalia region, known for its rural character and location near the Lower Rhine.
  • D. Hanworth
    Hanworth is a suburban residential area in west London, England, known for its parks, local amenities, and proximity to Heathrow Airport.
  • E. Olsberg
    Olsberg is a small town in the Hochsauerland region of North Rhine-Westphalia, Germany, known for its scenic location in the Sauerland hills and outdoor recreation opportunities.
  • 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.