Triple
T3454032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sardar Sarovar Dam |
E72857
|
entity |
| Predicate | designedIrrigationArea_ha |
P6177
|
FINISHED |
| Object | 1800000 |
—
|
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: 1800000 | Statement: [Sardar Sarovar Dam, designedIrrigationArea_ha, 1800000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedIrrigationArea_ha Context triple: [Sardar Sarovar Dam, designedIrrigationArea_ha, 1800000]
-
A.
hasIrrigationArea
chosen
Indicates that an entity possesses or is associated with a specific area of land equipped or designated for irrigation.
-
B.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
C.
irrigationProjectIn
Indicates that an irrigation project is located within or implemented in a specified geographic or administrative area.
-
D.
fieldDesign
Indicates a relationship where an entity is responsible for planning, arranging, or specifying the layout and structure of a particular field or area.
-
E.
hasBotanicalGardenArea_ha
Indicates that an entity possesses a botanical garden whose area is measured in hectares.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa457fc8190824ca00254e962f9 |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.