Triple
T28880098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gezira |
E732391
|
entity |
| Predicate | majorIrrigationProject |
P136581
|
FINISHED |
| Object | Gezira Scheme |
—
|
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: Gezira Scheme | Statement: [Gezira, majorIrrigationProject, Gezira Scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorIrrigationProject Context triple: [Gezira, majorIrrigationProject, Gezira Scheme]
-
A.
irrigationProjectIn
Indicates that an irrigation project is located within or implemented in a specified geographic or administrative area.
-
B.
majorInfrastructureProject
Indicates a large-scale, capital-intensive construction or development initiative that significantly impacts public systems, services, or facilities.
-
C.
majorDrainageWorksBy
Indicates that significant drainage construction or improvement works are carried out by a specified agent or organization.
-
D.
hasIrrigationSchemes
chosen
Indicates that an entity is associated with, implements, or contains one or more irrigation schemes.
-
E.
nearIrrigationProject
Indicates that one entity is located close to or in the vicinity of an irrigation project.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 28, 2026, 7:42 a.m.