Triple
T36620336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahr el Ghazal confluence |
E904018
|
entity |
| Predicate | riverJoins |
P11843
|
FINISHED |
| Object | Bahr el Ghazal River |
—
|
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: Bahr el Ghazal River | Statement: [Bahr el Ghazal confluence, riverJoins, Bahr el Ghazal River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverJoins Context triple: [Bahr el Ghazal confluence, riverJoins, Bahr el Ghazal River]
-
A.
riverConfluence
chosen
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
B.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
C.
riverAlsoKnownAs
Indicates that a river has an alternative name or alias by which it is also known.
-
D.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.