Triple
T19560183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gash River |
E489426
|
entity |
| Predicate | hasIrrigationSchemes |
P136581
|
FINISHED |
| Object | Gash irrigation schemes near Kassala |
—
|
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: Gash irrigation schemes near Kassala | Statement: [Gash River, hasIrrigationSchemes, Gash irrigation schemes near Kassala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIrrigationSchemes Context triple: [Gash River, hasIrrigationSchemes, Gash irrigation schemes near Kassala]
-
A.
irrigationScheme
Indicates that one entity is part of, served by, or associated with a particular irrigation scheme or system for water distribution.
-
B.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
C.
irrigationProjectIn
Indicates that an irrigation project is located within or implemented in a specified geographic or administrative area.
-
D.
hasWaterManagementStructure
Indicates that one entity possesses, contains, or is associated with a built feature used to control, store, convey, or manage water.
-
E.
typeOfIrrigation
Indicates the specific irrigation method or system used to supply water to a given area or crop.
- F. None of above. chosen
Provenance (4 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f731ae48190ade295c15db7f8ed |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51796b4c48190b721114dde654bd7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 1:42 p.m.