Triple
T25331617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganga–Hooghly water diversion |
E635165
|
entity |
| Predicate | divertsTo |
P40218
|
FINISHED |
| Object | Hooghly River |
—
|
NE NERFINISHED |
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: Hooghly River | Statement: [Ganga–Hooghly water diversion, divertsTo, Hooghly River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divertsTo Context triple: [Ganga–Hooghly water diversion, divertsTo, Hooghly River]
-
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.
divertedFrom
Indicates that something has been redirected or rerouted away from its original or intended course, destination, or target.
-
C.
hasDivertor
Indicates that an entity is equipped with or includes a divertor component as part of its design or configuration.
-
D.
directedTo
chosen
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
E.
diversionMethod
Indicates the method or tactic used to distract, mislead, or redirect attention or resources away from a primary target or activity.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c5f86c81908cf1ce29669bafbe |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:30 p.m.