Triple
T36270266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harare–Chirundu highway |
E892649
|
entity |
| Predicate | nearbyBorderTown |
P194246
|
FINISHED |
| Object | Chirundu |
—
|
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: Chirundu | Statement: [Harare–Chirundu highway, nearbyBorderTown, Chirundu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyBorderTown Context triple: [Harare–Chirundu highway, nearbyBorderTown, Chirundu]
-
A.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
B.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
C.
borderTerminusNearby
chosen
Indicates that the endpoint of a border or boundary lies close to a specified reference location or feature.
-
D.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
E.
nearbyTownSouth
Indicates that one town is located to the south and in close proximity to another town.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 3, 2026, 4:09 p.m.