Triple
T10295547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe–Zambia border |
E241475
|
entity |
| Predicate | naturalBoundaryForMostOfLength |
P84052
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zimbabwe–Zambia border, naturalBoundaryForMostOfLength, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalBoundaryForMostOfLength Context triple: [Zimbabwe–Zambia border, naturalBoundaryForMostOfLength, true]
-
A.
borderSectionLength
Indicates the measured length of a specific segment of a shared border between two geographic or administrative areas.
-
B.
typicalBoundary
chosen
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
C.
shareBorderLengthApprox
Indicates that two entities share a common boundary whose length is approximately equal to a specified value.
-
D.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
E.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds 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_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.