Triple
T11801244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shahjahanpur |
E280629
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Khannaut River |
E1232781
|
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: Khannaut River | Statement: [Shahjahanpur, hasRiver, Khannaut River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khannaut River Context triple: [Shahjahanpur, hasRiver, Khannaut River]
-
A.
Khannaut River
chosen
The Khannaut River is a regional river in northern India that flows through the city of Shahjahanpur in Uttar Pradesh.
-
B.
Nyukzha River
The Nyukzha River is a significant tributary waterway in eastern Siberia, Russia, contributing to the Olyokma River system within the Lena basin.
-
C.
Khimka River
The Khimka River is a small waterway in the Moscow Oblast of Russia that flows through the city of Khimki and into the Moscow Canal.
-
D.
Bahlui River
The Bahlui River is a significant river in northeastern Romania that flows through the city of Iași before joining the Jijia River.
-
E.
Khudosey River
The Khudosey River is a significant watercourse in northern Siberia, Russia, known as one of the main tributaries contributing to the Taz River basin.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a4512c8190b7782e1dee053000 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b272ea6c8190b22fd78081446701 |
completed | May 10, 2026, 4:29 p.m. |
Created at: April 8, 2026, 9:42 p.m.