Triple
T35815906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rusape Dam |
E1035357
|
entity |
| Predicate | isMajorReservoirFor |
P11014
|
FINISHED |
| Object | northeastern Zimbabwe |
—
|
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: northeastern Zimbabwe | Statement: [Rusape Dam, isMajorReservoirFor, northeastern Zimbabwe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorReservoirFor Context triple: [Rusape Dam, isMajorReservoirFor, northeastern Zimbabwe]
-
A.
hasMajorReservoir
Indicates that an entity possesses or is associated with a primary or significant reservoir (such as a large storage or accumulation of a resource).
-
B.
majorReservoir
chosen
Indicates that one entity functions as a primary or significant water-storage reservoir associated with another entity.
-
C.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
D.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
-
E.
isLargestReservoirIn
Indicates that one entity is the largest reservoir located within or associated with another entity (such as a region, river system, or administrative area).
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 4:06 p.m.