Triple
T9874883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perm Krai |
E240048
|
entity |
| Predicate | hasMajorRiver |
P165
|
FINISHED |
| Object | Vishera River |
E332304
|
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: Vishera River | Statement: [Perm Krai, hasMajorRiver, Vishera River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vishera River Context triple: [Perm Krai, hasMajorRiver, Vishera River]
-
A.
Vishera River
chosen
The Vishera River is a significant waterway in Russia’s Perm Krai, known for its scenic, largely untouched natural landscapes and role in the regional river system.
-
B.
Demjanka River
The Demjanka River is a lesser-known river in western Siberia that serves as a tributary within the extensive Irtysh–Ob river system of Russia.
-
C.
Severka River
The Severka River is a waterway in Russia that flows through the town of Voskresensk in the Moscow region.
-
D.
Zusha River
The Zusha River is a significant waterway in western Russia that feeds into the Oka River and contributes to its drainage basin.
-
E.
Tvertsa River
The Tvertsa River is a waterway in western Russia that flows through Tver Oblast and serves as a tributary of the Volga 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3f89fa081908b58956902c193cf |
completed | April 2, 2026, 12:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e23aeb6f9c8190a986af35bcf353f7 |
completed | April 17, 2026, 1:51 p.m. |
Created at: March 30, 2026, 8:37 p.m.