Triple
T3513146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okavango Delta |
E74242
|
entity |
| Predicate | floodWaterOrigin |
P12617
|
FINISHED |
| Object | summer rains in Angola |
—
|
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: summer rains in Angola | Statement: [Okavango Delta, floodWaterOrigin, summer rains in Angola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodWaterOrigin Context triple: [Okavango Delta, floodWaterOrigin, summer rains in Angola]
-
A.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
B.
waterOrigin
chosen
Indicates the source or starting location from which the water originates or is supplied.
-
C.
floodSeasonCause
Indicates the cause or contributing factor responsible for a particular flood season occurring.
-
D.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
E.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc2d0bf481909d1f19a87d147b63 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.