Triple

T18733256
Position Surface form Disambiguated ID Type / Status
Subject Venlo E458091 entity
Predicate borderCrossingWith P4105 FINISHED
Object Kaldenkirchen 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: Kaldenkirchen | Statement: [Venlo, borderCrossingWith, Kaldenkirchen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kaldenkirchen
Context triple: [Venlo, borderCrossingWith, Kaldenkirchen]
  • A. Kaldenkirchen chosen
    Kaldenkirchen is a town in western Germany near the Dutch border, known as a key cross-border transport point with direct access to major motorway routes.
  • B. Kaulsdorf
    Kaulsdorf is a residential locality in eastern Berlin, Germany, known for its mix of historic village center and post-war housing estates.
  • C. Odenkirchen
    Odenkirchen is a district in the city of Mönchengladbach in western Germany, historically a small town in North Rhine-Westphalia.
  • D. Altenkirchen
    Altenkirchen is a small town in the state of Rhineland-Palatinate in western Germany, known as a local administrative and commercial center in the Westerwald region.
  • E. Bromskirchen
    Bromskirchen is a small municipality in the Waldeck-Frankenberg district of Hesse, Germany, near the border with North Rhine-Westphalia.
  • 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_69d8d393ba9c8190a8b03b04ddbb0a09 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e56d791ab88190b333503f9b1ad0c0 completed April 20, 2026, 12:04 a.m.
Created at: April 10, 2026, 11:51 a.m.