Triple
T5353698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandi district |
E102636
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Uhl River |
E181833
|
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: Uhl River | Statement: [Mandi district, hasRiver, Uhl River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uhl River Context triple: [Mandi district, hasRiver, Uhl River]
-
A.
Uhl River
chosen
The Uhl River is a Himalayan river in the Indian state of Himachal Pradesh, known for flowing through the Kangra Valley and supporting local hydropower and irrigation.
-
B.
Wurm River
The Wurm River is a small river in western Germany that flows through the city of Aachen before joining the Rur.
-
C.
Ruwer River
The Ruwer River is a small river in western Germany known for flowing through the Ruwer wine region before joining the Moselle.
-
D.
Rock River
Rock River is a tributary of the Big Sioux River flowing through parts of Iowa and South Dakota in the United States.
-
E.
Rock River
Rock River is a major waterway in the Midwestern United States that flows through Wisconsin and Illinois before joining the Mississippi River.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86149774819084049a8785e3f2e0 |
completed | March 20, 2026, 5:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21dbc540819086aca16af1aa6213 |
completed | March 21, 2026, 10:55 p.m. |
Created at: March 20, 2026, 2:01 p.m.