Triple
T35397559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | east-central Sudan |
E1023122
|
entity |
| Predicate | hasIrrigationSchemeType |
P79075
|
FINISHED |
| Object | gravity-fed irrigation |
—
|
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: gravity-fed irrigation | Statement: [east-central Sudan, hasIrrigationSchemeType, gravity-fed irrigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIrrigationSchemeType Context triple: [east-central Sudan, hasIrrigationSchemeType, gravity-fed irrigation]
-
A.
hasIrrigationSchemes
Indicates that an entity is associated with, implements, or contains one or more irrigation schemes.
-
B.
irrigationScheme
Indicates that one entity is part of, served by, or associated with a particular irrigation scheme or system for water distribution.
-
C.
typeOfIrrigation
chosen
Indicates the specific irrigation method or system used to supply water to a given area or crop.
-
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_69f7953827b48190aec5b07f65a3b304 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.