Triple

T37937693
Position Surface form Disambiguated ID Type / Status
Subject Vioolsdrif border post E946392 entity
Predicate adjacentCountryBorderPost P194156 FINISHED
Object Noordoewer border post 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: Noordoewer border post | Statement: [Vioolsdrif border post, adjacentCountryBorderPost, Noordoewer border post]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adjacentCountryBorderPost
Context triple: [Vioolsdrif border post, adjacentCountryBorderPost, Noordoewer border post]
  • A. connectsToBorderPost
    Indicates that one entity is linked or leads directly to a border post, establishing a route or connection between them.
  • B. EUInternalBorder
    Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
  • C. borderPostName
    Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
  • D. borderTradePointWith
    Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
  • E. hasBorderPostWith
    Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
  • F. None of above. chosen

Provenance (4 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_69f76ef531ac8190ae6d99e5786e76ec completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd64bc86848190a49f451a8fc5cf1e completed May 8, 2026, 4:21 a.m.
PD Predicate disambiguation batch_69fd5ff4a648819090756d90fd195d9a completed May 8, 2026, 4 a.m.
PDg Predicate description generation batch_69fd64bb345c819096a35c72784a8ce3 completed May 8, 2026, 4:21 a.m.
Created at: May 3, 2026, 4:20 p.m.