Triple
T23971044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyimba |
E604231
|
entity |
| Predicate | borderingCountryViaRoadCorridor |
P84182
|
FINISHED |
| Object | Malawi |
—
|
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: Malawi | Statement: [Nyimba, borderingCountryViaRoadCorridor, Malawi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingCountryViaRoadCorridor Context triple: [Nyimba, borderingCountryViaRoadCorridor, Malawi]
-
A.
countryBorderingRegionLinkedByRoutes
Indicates that a country and a region share a border and are connected by established transportation or travel routes.
-
B.
countryBorderDirection
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
-
C.
bordersVia
chosen
Indicates that two entities share a boundary or border that is specifically established, defined, or mediated through a particular intermediate feature, route, or medium.
-
D.
borderingCountryContext
Indicates that one country shares a land or maritime boundary with another within a specified geopolitical or temporal context.
-
E.
borderingCountryOfRegion
Indicates that a country shares a land or maritime border with a specified geographic region.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dc3f088190a55faf6f01ddf4bf |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.