Triple
T3615810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indus Waters Treaty |
E76596
|
entity |
| Predicate | allocatesToCountry |
P50442
|
FINISHED |
| Object | western rivers to Pakistan |
—
|
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: western rivers to Pakistan | Statement: [Indus Waters Treaty, allocatesToCountry, western rivers to Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatesToCountry Context triple: [Indus Waters Treaty, allocatesToCountry, western rivers to Pakistan]
-
A.
usedByCountryCode
Indicates that something is utilized or applied within the country identified by the given country code.
-
B.
alsoInCountry
Indicates that something located in one country is additionally located or present in another specified country.
-
C.
displayedInCountry
Indicates that something is shown, exhibited, or made visible within the boundaries of a specified country.
-
D.
hasCountry
Indicates that one entity possesses, is associated with, or is located within a specific country.
-
E.
supportsCountry
Indicates that one entity provides assistance, endorsement, or backing to a specific country.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27b5e008190a72a8dab7d736e64 |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:23 p.m.