Triple
T38492801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulawayo–Plumtree Road |
E918099
|
entity |
| Predicate | connectsBorderPost |
P113298
|
FINISHED |
| Object | Plumtree Border Post |
—
|
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: Plumtree Border Post | Statement: [Bulawayo–Plumtree Road, connectsBorderPost, Plumtree Border Post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsBorderPost Context triple: [Bulawayo–Plumtree Road, connectsBorderPost, Plumtree Border Post]
-
A.
connectsToBorderPost
chosen
Indicates that one entity is linked or leads directly to a border post, establishing a route or connection between them.
-
B.
borderConnectivity
Indicates that two regions or areas are directly adjacent or connected along a shared boundary.
-
C.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
D.
crossBorderFacilityConnectsTo
Indicates that a cross-border facility provides a direct physical or operational connection between two locations or infrastructures across a border.
-
E.
connectsToCountryBorder
Indicates that one entity is directly adjacent to and touches the border of a specified country.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 3, 2026, 4:31 p.m.