Triple
T37937611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariamsvlei–Nakop crossing |
E946390
|
entity |
| Predicate | borderPostOf |
P113299
|
FINISHED |
| Object | Namibia |
—
|
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: Namibia | Statement: [Ariamsvlei–Nakop crossing, borderPostOf, Namibia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPostOf Context triple: [Ariamsvlei–Nakop crossing, borderPostOf, Namibia]
-
A.
borderPostIs
chosen
Indicates that one entity functions as a border post associated with or located at another entity.
-
B.
borderPostType
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
-
C.
borderPostName
Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
-
D.
borderPostHandles
Indicates that a particular border post is responsible for managing, processing, or overseeing a specified type of traffic, activity, or operation.
-
E.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: May 3, 2026, 4:20 p.m.