Triple
T37095813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesta Low Dam II |
E918557
|
entity |
| Predicate | hasHydraulicHeadType |
P187137
|
FINISHED |
| Object | low head |
—
|
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: low head | Statement: [Teesta Low Dam II, hasHydraulicHeadType, low head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydraulicHeadType Context triple: [Teesta Low Dam II, hasHydraulicHeadType, low head]
-
A.
hasHydraulicHead
Indicates that one entity possesses or is characterized by a specific hydraulic head value relative to another reference point or system.
-
B.
hasHydrologicalType
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
-
C.
waterHeadType
Indicates the type or classification of a water head (e.g., source or headwater) associated with a water-related feature.
-
D.
hasHydrologicalHierarchyLevel
Indicates the position or rank of a water-related feature within a structured hydrological hierarchy or network.
-
E.
hasHeadwaterStatus
Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.