Triple
T24376228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa–Mozambique border |
E614481
|
entity |
| Predicate | hasTerminusPoint |
P27716
|
FINISHED |
| Object | Tripoint with Eswatini |
—
|
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: Tripoint with Eswatini | Statement: [South Africa–Mozambique border, hasTerminusPoint, Tripoint with Eswatini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminusPoint Context triple: [South Africa–Mozambique border, hasTerminusPoint, Tripoint with Eswatini]
-
A.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
B.
hasTerminusRole
Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
-
C.
hasOppositeTerminus
Indicates that one terminus (end point) of an entity is directly opposite or facing the terminus of another entity.
-
D.
hasCapitalTerminus
Indicates that a transportation route or line has its endpoint located in a capital city.
-
E.
hasBorderTerminus
chosen
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d73c0c8190b80e257845a04c57 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.