Triple
T37616803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basoga |
E935945
|
entity |
| Predicate | regionMainRiver |
P155048
|
FINISHED |
| Object | Nile 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: Nile River | Statement: [Basoga, regionMainRiver, Nile River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionMainRiver Context triple: [Basoga, regionMainRiver, Nile River]
-
A.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
B.
isRegionalRiver
Indicates that a river is classified as a regional river, typically limited in geographic extent and significance to a specific region rather than being a major or national waterway.
-
C.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
D.
primaryRiverRegion
chosen
Indicates that a given region is the main geographic area through which a particular river primarily flows or with which it is chiefly associated.
-
E.
mainRiverAssociated
Indicates that one entity is associated with, or primarily linked to, a particular main river.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 3, 2026, 4:18 p.m.