Triple
T36240119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namibia–Angola border |
E891495
|
entity |
| Predicate | adjacentToAngolanProvince |
P68114
|
FINISHED |
| Object | Cunene Province |
—
|
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: Cunene Province | Statement: [Namibia–Angola border, adjacentToAngolanProvince, Cunene Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentToAngolanProvince Context triple: [Namibia–Angola border, adjacentToAngolanProvince, Cunene Province]
-
A.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
B.
geographicallyAdjacentTo
chosen
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
C.
areaRankInAngola
Indicates the relative position of an entity in a ranking ordered by its area size within Angola.
-
D.
borderTypeWithAngola
Indicates the type or nature of the border relationship that an entity has with Angola.
-
E.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:09 p.m.