Triple
T2048364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kagera River |
E45505
|
entity |
| Predicate | isPrimaryOutflowFor |
P967
|
FINISHED |
| Object | parts of Rwanda |
—
|
LITERAL 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: parts of Rwanda | Statement: [Kagera River, isPrimaryOutflowFor, parts of Rwanda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryOutflowFor Context triple: [Kagera River, isPrimaryOutflowFor, parts of Rwanda]
-
A.
hasPrimaryInflow
Indicates that one entity serves as the main source of inflowing material, energy, or influence into another entity.
-
B.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
C.
outflow
chosen
Indicates the movement or discharge of something from an origin or source to the outside or to another location.
-
D.
regulatesOutflowOf
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
-
E.
isPrimaryFacilityFor
Indicates that one facility serves as the main or principal location responsible for supporting or serving a particular entity or operation.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98c70c48190beb98aad56d9daf1 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.