Triple
T13534226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zambia and Zimbabwe |
E323217
|
entity |
| Predicate | shareGeologicalFeature |
P110735
|
FINISHED |
| Object | Zambezi River gorge system |
—
|
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: Zambezi River gorge system | Statement: [Zambia and Zimbabwe, shareGeologicalFeature, Zambezi River gorge system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareGeologicalFeature Context triple: [Zambia and Zimbabwe, shareGeologicalFeature, Zambezi River gorge system]
-
A.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
B.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
-
C.
physicalFeature
Indicates that one entity possesses or exhibits a particular physical characteristic or attribute.
-
D.
nearGeologicalSite
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
E.
geographicalAnomaly
Indicates a relationship where a location exhibits unusual or irregular geographical features or conditions compared to its surrounding area.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbcad2881909fb7490311807f75 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.