Triple
T4188951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skardu |
E88385
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Satpara Stream |
E395900
|
NE 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: Satpara Stream | Statement: [Skardu, locatedOnRiver, Satpara Stream]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Satpara Stream Context triple: [Skardu, locatedOnRiver, Satpara Stream]
-
A.
Satpara Stream
chosen
Satpara Stream is a mountain watercourse in Gilgit-Baltistan, Pakistan, that carries glacial and lake-fed waters from the Skardu region downstream.
-
B.
Gaja stream
Gaja stream is a small river in Hungary that flows through the city of Székesfehérvár and its surrounding region.
-
C.
Baspa River
The Baspa River is a Himalayan river in Himachal Pradesh, India, known for flowing through the scenic Kinnaur region and the Baspa (Sangla) Valley before joining the Sutlej.
-
D.
Sainj River
The Sainj River is a Himalayan river in Himachal Pradesh, India, known for flowing through the ecologically rich and protected landscapes of the Great Himalayan National Park.
-
E.
Pakhra River
The Pakhra River is a tributary waterway in the Moscow region of Russia that feeds into the larger Moskva River system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0326eaec819083cd298c9219dd15 |
completed | March 9, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b58a034f6481909a3126d8832f7821 |
completed | March 14, 2026, 4:17 p.m. |
Created at: March 9, 2026, 3:46 p.m.