Triple
T19973847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molopo River basin |
E493635
|
entity |
| Predicate | surfaceWaterAvailability |
P45851
|
FINISHED |
| Object | seasonal |
—
|
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: seasonal | Statement: [Molopo River basin, surfaceWaterAvailability, seasonal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceWaterAvailability Context triple: [Molopo River basin, surfaceWaterAvailability, seasonal]
-
A.
freshwaterAvailability
Indicates the degree to which usable freshwater resources are present and accessible in a given context.
-
B.
surfaceWater
chosen
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
C.
hasWaterResourceRole
Indicates that an entity participates in a water-related resource context with a specified functional role (e.g., source, user, manager, or regulator of water resources).
-
D.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
E.
waterPresence
Indicates the existence or amount of water present in or around a specified entity or location.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65bcb72048190aedb4f085ace0493 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:17 p.m.