Triple
T37965298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariamsvlei border post |
E947124
|
entity |
| Predicate | borderWithCountrySide |
P70148
|
FINISHED |
| Object | South African side at Nakop |
—
|
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: South African side at Nakop | Statement: [Ariamsvlei border post, borderWithCountrySide, South African side at Nakop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderWithCountrySide Context triple: [Ariamsvlei border post, borderWithCountrySide, South African side at Nakop]
-
A.
borderCountrySide
chosen
Indicates that one country shares a land border with the side or region of another country.
-
B.
borderWithTerritory
Indicates that one territory shares a common boundary or border with another territory.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
E.
borderCultureWith
Indicates that two regions or entities share a common boundary across which cultural traits, practices, or influences are actively exchanged or intertwined.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:20 p.m.