Triple
T35397582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | east-central Sudan |
E1023122
|
entity |
| Predicate | usesIrrigationWater |
P155364
|
FINISHED |
| Object | Blue Nile |
—
|
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: Blue Nile | Statement: [east-central Sudan, usesIrrigationWater, Blue Nile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIrrigationWater Context triple: [east-central Sudan, usesIrrigationWater, Blue Nile]
-
A.
usedIrrigation
Indicates that an entity applied or employed an irrigation system or method to supply water to land or crops.
-
B.
usedForIrrigationIn
chosen
Indicates that something serves as a means or resource for irrigating land or crops in a specified location or context.
-
C.
usedIrrigationFrom
Indicates that one entity applied or relied on irrigation resources, systems, or methods originating from another entity.
-
D.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
E.
hasIrrigationDependence
Indicates that one entity relies on another entity or system to provide irrigation for its water needs.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.