Triple
T37937661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vioolsdrif border post |
E946392
|
entity |
| Predicate | hasCounterpartBorderPost |
—
|
GENERATED |
| Object | Noordoewer border post |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCounterpartBorderPost Context triple: [Vioolsdrif border post, hasCounterpartBorderPost, Noordoewer border post]
-
A.
hasBorderPostWith
chosen
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
B.
connectsToBorderPost
Indicates that one entity is linked or leads directly to a border post, establishing a route or connection between them.
-
C.
adjacentCountryBorderPost
Indicates that a border post is located at or associated with the boundary between two adjacent countries.
-
D.
hasBorderCrossingSide
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
-
E.
hasBorderCrossingsType
Indicates that a border crossing is classified by a specific type or category of crossing (e.g., road, rail, pedestrian, maritime).
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:20 p.m.