Triple
T15011381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NH19 |
E377843
|
entity |
| Predicate | connectsRiverValley |
P116349
|
FINISHED |
| Object | Ganga river basin |
—
|
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: Ganga river basin | Statement: [NH19, connectsRiverValley, Ganga river basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRiverValley Context triple: [NH19, connectsRiverValley, Ganga river basin]
-
A.
connectsCityToRiver
Indicates a relationship where a city is linked or joined to a river, typically via infrastructure such as roads, bridges, or transport routes.
-
B.
locatedInRiverValley
Indicates that something is situated within the geographical area of a river valley.
-
C.
waterwayLinkBetween
Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
-
D.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
-
E.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7613cec8190ac25e3f68c5d0edf |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:55 a.m.