Triple

T36293140
Position Surface form Disambiguated ID Type / Status
Subject Westerkappeln E893285 entity
Predicate isCloseToStateBorder P144886 FINISHED
Object North Rhine-Westphalia–Lower Saxony border LITERAL 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: North Rhine-Westphalia–Lower Saxony border | Statement: [Westerkappeln, isCloseToStateBorder, North Rhine-Westphalia–Lower Saxony border]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCloseToStateBorder
Context triple: [Westerkappeln, isCloseToStateBorder, North Rhine-Westphalia–Lower Saxony border]
  • A. borderStateNearby
    Indicates that one state is geographically close to, but does not necessarily directly touch, the border of another state.
  • B. locatedNearStateBorderWith
    Indicates that one entity is situated geographically close to the border of a specified state.
  • C. nearInternationalBoundary
    Indicates that one entity is located close to an international boundary separating two or more countries.
  • D. nearStateBorderWith chosen
    Indicates that one entity is located close to the state border shared with another specified state or region.
  • E. hasNearbyCountyBorder
    Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
  • F. None of above.

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_69f76e4a61f0819084a2b68dbbb4efc6 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba6d06f48190a71b5a2f19e2232f completed May 3, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:09 p.m.