Triple
T36620343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahr el Ghazal confluence |
E904018
|
entity |
| Predicate | watercourse2 |
P160925
|
FINISHED |
| Object | White Nile |
—
|
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: White Nile | Statement: [Bahr el Ghazal confluence, watercourse2, White Nile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourse2 Context triple: [Bahr el Ghazal confluence, watercourse2, White Nile]
-
A.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
B.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
-
C.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
-
D.
watercourseHelpsForm
chosen
Indicates that a watercourse contributes to the creation, shaping, or delineation of another geographic feature or boundary.
-
E.
watercourseSupports
Indicates that a watercourse provides the necessary conditions or resources to sustain another entity, process, or activity.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4:11 p.m.