Triple

T29971306
Position Surface form Disambiguated ID Type / Status
Subject Ems River basin E761324 entity
Predicate hasTransboundarySection P173239 FINISHED
Object German–Dutch border region 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: German–Dutch border region | Statement: [Ems River basin, hasTransboundarySection, German–Dutch border region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransboundarySection
Context triple: [Ems River basin, hasTransboundarySection, German–Dutch border region]
  • A. hasInternationalBorderSection
    Indicates that one entity shares a specific segment or portion of its international border with another entity.
  • B. crossBorderSection chosen
    Indicates a section or segment that extends across or passes from one jurisdiction, region, or country into another.
  • C. transboundaryContext
    Indicates a context, situation, or effect that crosses or involves the boundaries between two or more distinct jurisdictions, regions, or territories.
  • D. hasHydrologicalBoundary
    Indicates that one entity serves as a hydrological boundary or limit for another, typically defining the extent of a water-related area or system.
  • E. isSharedWatercourseBetween
    Indicates that a watercourse (such as a river, stream, or canal) is jointly used, bordered, or managed by two or more distinct entities (e.g., regions, countries, or properties).
  • 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_69f22467626081908d5afea489590e96 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fe21b0cba48190b56c39e9f1c0eafa completed May 8, 2026, 5:47 p.m.
PD Predicate disambiguation batch_69fe204576848190aecf204e2adba5dc completed May 8, 2026, 5:41 p.m.
Created at: April 29, 2026, 6:32 p.m.