Triple
T9620607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narmada Water Disputes Tribunal Award |
E232331
|
entity |
| Predicate | disputeReferredYear |
P89296
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Narmada Water Disputes Tribunal Award, disputeReferredYear, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeReferredYear Context triple: [Narmada Water Disputes Tribunal Award, disputeReferredYear, 1969]
-
A.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
-
B.
notableCaseYear
Indicates the year in which a particular case became notable or gained recognized significance.
-
C.
wasOverturnedInYear
Indicates that a prior decision, ruling, or outcome was reversed or nullified in the specified year.
-
D.
yearOfReference
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
E.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad3a8d88190b1414aa676d82f36 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:09 p.m.