Triple
T3212116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwestern Zambia |
E67303
|
entity |
| Predicate | borderDirection |
P27801
|
FINISHED |
| Object | borders Angola to the west |
—
|
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: borders Angola to the west | Statement: [Northwestern Zambia, borderDirection, borders Angola to the west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirection Context triple: [Northwestern Zambia, borderDirection, borders Angola to the west]
-
A.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
B.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
C.
countryBorderDirection
chosen
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
-
D.
borderCharacteristic
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
-
E.
borderText
Indicates that one entity is the textual content displayed along the 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaaba224c8190ad2f4e0ed1c2ca4a |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.