Triple
T29337655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swargarohini |
E743952
|
entity |
| Predicate | liesInWatershedOf |
P58176
|
FINISHED |
| Object | Yamuna 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: Yamuna River | Statement: [Swargarohini, liesInWatershedOf, Yamuna River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesInWatershedOf Context triple: [Swargarohini, liesInWatershedOf, Yamuna River]
-
A.
hasWatershedWith
chosen
Indicates that two geographic areas share or are associated with the same watershed or drainage basin.
-
B.
hydrologicallyConnectedTo
Indicates that two water bodies or hydrological features are linked such that water can flow or be transferred between them, directly or indirectly, through the hydrological system.
-
C.
isPrincipalBasinOf
Indicates that one basin serves as the main or primary drainage basin associated with another geographic or hydrologic feature.
-
D.
liesOnWatershedBetween
Indicates that something is located on or along the dividing line between two drainage basins or watersheds.
-
E.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6692495f0819093b2d49db448ee42 |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:31 p.m.