Triple
T36270256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harare–Chirundu highway |
E892649
|
entity |
| Predicate | endpointBorder |
P93185
|
FINISHED |
| Object | Zimbabwe–Zambia border |
—
|
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: Zimbabwe–Zambia border | Statement: [Harare–Chirundu highway, endpointBorder, Zimbabwe–Zambia border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointBorder Context triple: [Harare–Chirundu highway, endpointBorder, Zimbabwe–Zambia border]
-
A.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
B.
borderTypeAtTerminusB
Indicates the type or classification of the border present at the second (B) endpoint of a defined boundary or connection.
-
C.
borderTerminus
chosen
Indicates the endpoint location where a border between two areas or entities begins or ends.
-
D.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
E.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
- 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_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.