Triple
T34915226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mata-Mata (Namibia) |
E1006981
|
entity |
| Predicate | borderOppositeSettlement |
P46520
|
FINISHED |
| Object | Mata-Mata Rest Camp (South Africa) |
—
|
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: Mata-Mata Rest Camp (South Africa) | Statement: [Mata-Mata (Namibia), borderOppositeSettlement, Mata-Mata Rest Camp (South Africa)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderOppositeSettlement Context triple: [Mata-Mata (Namibia), borderOppositeSettlement, Mata-Mata Rest Camp (South Africa)]
-
A.
borderSettlement
chosen
Indicates that a settlement is located near or along a political or administrative border.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
D.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: May 3, 2026, 4 p.m.