Triple
T2083476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shillong |
E45294
|
entity |
| Predicate | riverNearby |
P15504
|
FINISHED |
| Object | Umshyrpi River |
E315896
|
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: Umshyrpi River | Statement: [Shillong, riverNearby, Umshyrpi River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Umshyrpi River Context triple: [Shillong, riverNearby, Umshyrpi River]
-
A.
Adhaim River
The Adhaim River is a significant river in Iraq that flows through the northeastern part of the country before joining the Tigris.
-
B.
Shashe River
The Shashe River is a significant watercourse in southern Africa that flows through Botswana and Zimbabwe before joining the Limpopo River.
-
C.
Imnaha River
The Imnaha River is a remote, scenic river in northeastern Oregon known for its rugged canyon landscapes and contributions to the Snake River watershed.
-
D.
Rukni River
chosen
The Rukni River is a lesser-known tributary stream that feeds into the larger Barak River system in northeastern India.
-
E.
Nyari River
The Nyari River is a regional river in the Indian state of Gujarat that flows through and helps sustain the city of Rajkot.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba524b60819089a11957ce6dbc4b |
completed | March 7, 2026, 5:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5db49ec24819098594c395bc88fe8 |
completed | March 14, 2026, 10:03 p.m. |
Created at: March 4, 2026, 7:41 p.m.