Triple
T25577893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jatigede Dam |
E641160
|
entity |
| Predicate | irrigationAreaServed |
P6177
|
FINISHED |
| Object | approximately 90000 hectares |
—
|
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: approximately 90000 hectares | Statement: [Jatigede Dam, irrigationAreaServed, approximately 90000 hectares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: irrigationAreaServed Context triple: [Jatigede Dam, irrigationAreaServed, approximately 90000 hectares]
-
A.
hasIrrigationArea
chosen
Indicates that an entity possesses or is associated with a specific area of land equipped or designated for irrigation.
-
B.
developedWithIrrigationDistrict
Indicates that something was created, built, or carried out in collaboration with, or under the auspices of, an irrigation district.
-
C.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
D.
feedsIrrigationDistrict
Indicates that one water source or system supplies water to an irrigation district.
-
E.
usedIrrigation
Indicates that an entity applied or employed an irrigation system or method to supply water to land or crops.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f931bdd88190ac4bf404087f4c83 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 4:02 p.m.