Triple
T25275945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunduma–Nakonde border |
E633695
|
entity |
| Predicate | hasBorderTownOnZambianSide |
P159423
|
FINISHED |
| Object | Nakonde |
—
|
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: Nakonde | Statement: [Tunduma–Nakonde border, hasBorderTownOnZambianSide, Nakonde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderTownOnZambianSide Context triple: [Tunduma–Nakonde border, hasBorderTownOnZambianSide, Nakonde]
-
A.
hasBorderTownOnTanzanianSide
Indicates that a specified town lies on the Tanzanian side of an international border shared with another country.
-
B.
hasBorderTownOnMyanmarSide
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
C.
hasBorderTownOnCanadianSide
Indicates that one location has a corresponding border town situated on the Canadian side of an international boundary.
-
D.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
E.
borderDistanceToMalawi_km
Indicates the distance in kilometers from an entity’s border to the border of Malawi.
- F. None of above. chosen
Provenance (4 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f584f07b648190aee894c1d5320bc3 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 1:17 p.m.