Triple
T37937890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesotho Highlands Water Project |
E946397
|
entity |
| Predicate | waterRecipient |
P4102
|
FINISHED |
| Object | Vaal River System |
—
|
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: Vaal River System | Statement: [Lesotho Highlands Water Project, waterRecipient, Vaal River System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterRecipient Context triple: [Lesotho Highlands Water Project, waterRecipient, Vaal River System]
-
A.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
feedsWatersThatReach
Indicates that one body of water supplies or contributes flow to other waters that it eventually reaches.
-
C.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
D.
watercourseHelpsForm
Indicates that a watercourse contributes to the creation, shaping, or delineation of another geographic feature or boundary.
-
E.
watercourseTypeServed
Indicates the type of watercourse (e.g., river, canal, stream) that is supplied, supported, or otherwise served by a given feature or system.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 3, 2026, 4:20 p.m.