Triple
T25238391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Ganges-Yamuna Doab |
E632398
|
entity |
| Predicate | majorRiverBoundary |
P122362
|
FINISHED |
| Object | Ganges 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: Ganges River | Statement: [Upper Ganges-Yamuna Doab, majorRiverBoundary, Ganges River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRiverBoundary Context triple: [Upper Ganges-Yamuna Doab, majorRiverBoundary, Ganges River]
-
A.
transboundaryRiverOf
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
B.
transboundaryBasin
Indicates that a river basin or watershed extends across and is shared by the territories of two or more political or administrative jurisdictions.
-
C.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
D.
borderingWaters
chosen
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
-
E.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 1:07 p.m.