Triple
T25553147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamuno Border Post |
E640496
|
entity |
| Predicate | nearbyCountryTownOnNamibiaSide |
P170333
|
FINISHED |
| Object | Buitepos |
—
|
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: Buitepos | Statement: [Mamuno Border Post, nearbyCountryTownOnNamibiaSide, Buitepos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCountryTownOnNamibiaSide Context triple: [Mamuno Border Post, nearbyCountryTownOnNamibiaSide, Buitepos]
-
A.
hasBorderTownOnZambianSide
Indicates that a town is located on the Zambian side of a border shared with another country.
-
B.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
C.
hasBorderTownOnTanzanianSide
Indicates that a specified town lies on the Tanzanian side of an international border shared with another country.
-
D.
distanceToSwakopmund
Indicates the spatial distance between a given entity’s location and the town of Swakopmund.
-
E.
timeZoneSideNamibia
Indicates that one entity is located on the Namibian side of a time zone boundary or division.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 21, 2026, 3:38 p.m.