Triple
T7525209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beas–Sutlej link |
E177873
|
entity |
| Predicate | typeOfDiversion |
P67992
|
FINISHED |
| Object | gravity canal diversion |
—
|
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: gravity canal diversion | Statement: [Beas–Sutlej link, typeOfDiversion, gravity canal diversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDiversion Context triple: [Beas–Sutlej link, typeOfDiversion, gravity canal diversion]
-
A.
divertedBy
Indicates that the normal course, flow, or direction of something is changed or rerouted due to the influence or action of another entity.
-
B.
diversionMethod
Indicates the method or tactic used to distract, mislead, or redirect attention or resources away from a primary target or activity.
-
C.
typeOfDivision
Indicates the specific category or kind of division that characterizes how something is separated, organized, or partitioned.
-
D.
driftType
Indicates the manner or category of deviation or change from an expected or original state.
-
E.
bypassType
chosen
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c7ac5c8190bbf9befdff791de0 |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.