Triple
T32548585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nile–Congo divide |
E831910
|
entity |
| Predicate | separatesRiverSystem |
P116581
|
FINISHED |
| Object | Nile 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: Nile River system | Statement: [Nile–Congo divide, separatesRiverSystem, Nile River system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesRiverSystem Context triple: [Nile–Congo divide, separatesRiverSystem, Nile River system]
-
A.
separatesRiverSystemsFlowingTo
chosen
Indicates that one entity acts as a dividing feature that causes river systems on either side to flow toward different drainage basins or destinations.
-
B.
separatesRiver
Indicates that a river serves as a dividing line or boundary between two entities.
-
C.
riverSeparatingFrom
Indicates that one river branches off or diverges from another river, creating a separation between their flow paths.
-
D.
tributarySystem
Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
-
E.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:02 a.m.