Triple
T36240125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namibia–Angola border |
E891495
|
entity |
| Predicate | hasNorthernCountry |
P123173
|
FINISHED |
| Object | Angola |
E12616
|
NE 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: Angola | Statement: [Namibia–Angola border, hasNorthernCountry, Angola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthernCountry Context triple: [Namibia–Angola border, hasNorthernCountry, Angola]
-
A.
hasNeighboringCountryToNorth
chosen
Indicates that one country is directly adjacent to and located south of another country, which lies to its north.
-
B.
hasNorthernmostIsland
Indicates that one geographic entity possesses or contains the island located furthest to the north within a specified area or group.
-
C.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
D.
hasMajorIslandOnNorthernBoundary
Indicates that the northern boundary of an entity is defined or significantly bordered by a major island.
-
E.
northernBorderLiesAcross
Indicates that the northern border of one region extends across or passes through the area of another region.
- F. None of above.
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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d71ff7c8190a707acdd42813578 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.