Triple

T17767253
Position Surface form Disambiguated ID Type / Status
Subject Vychegda River E443538 entity
Predicate hasCityOnBank P7935 FINISHED
Object Kotlas NE NERFINISHED

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: Kotlas | Statement: [Vychegda River, hasCityOnBank, Kotlas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kotlas
Context triple: [Vychegda River, hasCityOnBank, Kotlas]
  • A. Kotlas chosen
    Kotlas is a significant industrial and transport hub in northern Russia, located at the confluence of the Vychegda and Northern Dvina rivers.
  • B. Kholmsk
    Kholmsk is a port town on the western coast of Sakhalin Island in Russia, serving as an important maritime transport hub in the Sea of Japan.
  • C. Kotzebue
    Kotzebue is a remote city in northwestern Alaska located above the Arctic Circle, known as a regional hub for transportation, commerce, and Inupiat culture.
  • D. Kurilsk
    Kurilsk is a small Russian town on Iturup Island in the Kuril archipelago, serving as an administrative and fishing center in the North Pacific.
  • E. Setka
    Setka was an ancient Egyptian prince of the 4th Dynasty, likely a son of Pharaoh Djedefre, known from statues and inscriptions found at Abu Rawash.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9edf16c8190a59ebd245d378f4f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e485fccb9881908923564bf319f3c1 completed April 19, 2026, 7:36 a.m.
Created at: April 10, 2026, 10:11 a.m.