Triple
T9260653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudd |
E222568
|
entity |
| Predicate | floodingCause |
P31770
|
FINISHED |
| Object | seasonal variations in White Nile flow |
—
|
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 variations in White Nile flow | Statement: [Sudd, floodingCause, seasonal variations in White Nile flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodingCause Context triple: [Sudd, floodingCause, seasonal variations in White Nile flow]
-
A.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
B.
floodSeasonCause
chosen
Indicates the cause or contributing factor responsible for a particular flood season occurring.
-
C.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
D.
floodConsequence
Indicates the resulting effects, outcomes, or impacts that occur as a consequence of a flood event.
-
E.
floodEventMotivation
Indicates the underlying reason, cause, or driving factor that led to the occurrence of a specific flood event.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07175be881908a917573ec9b9081 |
completed | April 1, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.