Triple
T21284222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maputo Province |
E524609
|
entity |
| Predicate | hasBorderPostWithEswatini |
P39987
|
FINISHED |
| Object | Namaacha border post |
—
|
LITERAL 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: Namaacha border post | Statement: [Maputo Province, hasBorderPostWithEswatini, Namaacha border post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderPostWithEswatini Context triple: [Maputo Province, hasBorderPostWithEswatini, Namaacha border post]
-
A.
hasBorderPostWith
chosen
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
B.
connectsToBorderPost
Indicates that one entity is linked or leads directly to a border post, establishing a route or connection between them.
-
C.
hasBorderMeetingCountry
Indicates that one country shares a land or maritime border with another country.
-
D.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
E.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d4e7f881909c2cc7936a66b79d |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.