Triple
T26995020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gharsana |
E679958
|
entity |
| Predicate | hasIrrigationMethod |
P79075
|
FINISHED |
| Object | canal-based irrigation network |
—
|
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: canal-based irrigation network | Statement: [Gharsana, hasIrrigationMethod, canal-based irrigation network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIrrigationMethod Context triple: [Gharsana, hasIrrigationMethod, canal-based irrigation network]
-
A.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
B.
typeOfIrrigation
chosen
Indicates the specific irrigation method or system used to supply water to a given area or crop.
-
C.
hasIrrigationDependence
Indicates that one entity relies on another entity or system to provide irrigation for its water needs.
-
D.
hasIrrigationArea
Indicates that an entity possesses or is associated with a specific area of land equipped or designated for irrigation.
-
E.
hasIrrigatedAgriculture
Indicates that an entity engages in or possesses agricultural activities that are supported or sustained by artificial irrigation systems.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62193767c8190ac69cafd971a66f6 |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:54 a.m.