Triple
T32548579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nile–Congo divide |
E831910
|
entity |
| Predicate | relatedBasin |
P164428
|
FINISHED |
| Object | White Nile Basin |
E902322
|
NE 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: White Nile Basin | Statement: [Nile–Congo divide, relatedBasin, White Nile Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedBasin Context triple: [Nile–Congo divide, relatedBasin, White Nile Basin]
-
A.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
B.
basinFor
Indicates that something serves as a basin or receptacle specifically intended for collecting, holding, or draining another entity.
-
C.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
D.
resourceBasin
Indicates a relationship where a basin serves as a source or reservoir of resources for another entity or area.
-
E.
basinInteractsWith
chosen
Indicates that one basin affects or exchanges material, energy, or influence with another basin through some form of interaction.
- F. None of above.
Provenance (4 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3485ff77648190b1c9c2668b8d3c06 |
completed | June 18, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:02 a.m.