Triple
T516584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaveri |
E10721
|
entity |
| Predicate | dispute |
P1783
|
FINISHED |
| Object | Cauvery water sharing 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: Cauvery water sharing dispute | Statement: [Kaveri, dispute, Cauvery water sharing dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dispute Context triple: [Kaveri, dispute, Cauvery water sharing dispute]
-
A.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
-
B.
controversy
chosen
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
C.
disputePolicy
Indicates that there is a formal disagreement or conflict regarding a policy, typically triggering procedures for review, negotiation, or resolution.
-
D.
disputedAspect
Indicates that a particular feature, detail, or component of something is subject to disagreement or contention between parties.
-
E.
dissentClaimed
Indicates that an entity has expressed disagreement or opposition to a claim made by another entity.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f184c3a481909bf60bb627b0ea88 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.