Triple
T32533906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhima Irrigation Project |
E831536
|
entity |
| Predicate | stateIrrigationProjectOf |
P39313
|
FINISHED |
| Object | Maharashtra |
—
|
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: Maharashtra | Statement: [Bhima Irrigation Project, stateIrrigationProjectOf, Maharashtra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateIrrigationProjectOf Context triple: [Bhima Irrigation Project, stateIrrigationProjectOf, Maharashtra]
-
A.
irrigationProjectIn
chosen
Indicates that an irrigation project is located within or implemented in a specified geographic or administrative area.
-
B.
nearIrrigationProject
Indicates that one entity is located close to or in the vicinity of an irrigation project.
-
C.
hasIrrigationSchemes
Indicates that an entity is associated with, implements, or contains one or more irrigation schemes.
-
D.
stateProject
Indicates that a project is initiated, funded, or directly administered by a governmental state authority.
-
E.
feedsIrrigationDistrict
Indicates that one water source or system supplies water to an irrigation district.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 1:01 a.m.