Triple
T25620608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skilpadshek Border Post |
E642284
|
entity |
| Predicate | hasBorderPartner |
P39987
|
FINISHED |
| Object | Lobatse 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: Lobatse Border Post | Statement: [Skilpadshek Border Post, hasBorderPartner, Lobatse Border Post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderPartner Context triple: [Skilpadshek Border Post, hasBorderPartner, Lobatse Border Post]
-
A.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
B.
crossBorderPartner
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
-
C.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
D.
hasBorderPostWith
chosen
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
E.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 5:04 p.m.