Triple
T29935040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cauvery River basin |
E760334
|
entity |
| Predicate | interStateDispute |
P107087
|
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: [Cauvery River basin, interStateDispute, Cauvery water sharing dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interStateDispute Context triple: [Cauvery River basin, interStateDispute, Cauvery water sharing dispute]
-
A.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
B.
disputeIssue
chosen
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
-
C.
significantDispute
Indicates a serious, often prolonged disagreement or conflict exists between the involved entities.
-
D.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
E.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 29, 2026, 6:20 p.m.