Triple
T24010782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirpur |
E594523
|
entity |
| Predicate | waterConservationFeature |
P154855
|
FINISHED |
| Object | deep continuous contour trenches |
—
|
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: deep continuous contour trenches | Statement: [Shirpur, waterConservationFeature, deep continuous contour trenches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterConservationFeature Context triple: [Shirpur, waterConservationFeature, deep continuous contour trenches]
-
A.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
B.
waterFunction
Indicates that one entity serves a particular role, purpose, or function in relation to water (e.g., how it uses, manages, affects, or interacts with water).
-
C.
waterFeature
Indicates the presence of a natural or artificial body or flow of water associated with the subject.
-
D.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
E.
waterPersistence
Indicates how long water remains present or effective in a given context before dissipating, evaporating, or being removed.
- F. None of above. chosen
Provenance (4 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d59c762481909cf08491a39aec1b |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:41 p.m.