Triple
T10295567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe–Zambia border |
E241475
|
entity |
| Predicate | becameInternationalBorderForZimbabwe |
P77377
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [Zimbabwe–Zambia border, becameInternationalBorderForZimbabwe, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameInternationalBorderForZimbabwe Context triple: [Zimbabwe–Zambia border, becameInternationalBorderForZimbabwe, 1980]
-
A.
becameInternationalBorderInYear
chosen
Indicates that a boundary between entities started functioning as an international border in the specified year.
-
B.
countryStatusInZimbabwe
Indicates the legal or diplomatic status that an entity holds within or in relation to Zimbabwe.
-
C.
statusInZimbabwe
Indicates the legal, social, or official standing or condition that an entity holds within the context of Zimbabwe.
-
D.
sharesInternationalBorderWith
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
-
E.
demilitarizedBorderWith
Indicates that a border between two entities exists where military forces, installations, and activities are restricted or prohibited by agreement.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ea9b3c8190b11518b259d5825c |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:43 a.m.