Triple
T33195578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mullaperiyar Dam |
E849747
|
entity |
| Predicate | maximumWaterLevelControversy |
P63606
|
FINISHED |
| Object | 136 feet vs 142 feet dispute |
—
|
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: 136 feet vs 142 feet dispute | Statement: [Mullaperiyar Dam, maximumWaterLevelControversy, 136 feet vs 142 feet dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumWaterLevelControversy Context triple: [Mullaperiyar Dam, maximumWaterLevelControversy, 136 feet vs 142 feet dispute]
-
A.
waterSharingDispute
chosen
Indicates a conflict or disagreement between parties over the allocation, use, or control of water resources.
-
B.
waterLevelThreat
Indicates that the current water level poses a potential danger or risk relative to a defined safety threshold.
-
C.
hasNormalWaterLevel
Indicates that an entity’s water level is within the expected or standard range, neither abnormally high nor low.
-
D.
waterLevelHigherThan
Indicates that the water level of one entity is greater than the water level of another entity.
-
E.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:29 a.m.