Triple

T15505155
Position Surface form Disambiguated ID Type / Status
Subject Onega River E379061 entity
Predicate mouthLocation P417 FINISHED
Object Onega Bay E301810 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: Onega Bay | Statement: [Onega River, mouthLocation, Onega Bay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Onega Bay
Context triple: [Onega River, mouthLocation, Onega Bay]
  • A. Onega Bay chosen
    Onega Bay is a large southern inlet of Russia’s White Sea, known for its numerous islands, shallow waters, and importance to regional fishing and navigation.
  • B. Aniva Bay
    Aniva Bay is a coastal bay on the southeastern coast of Sakhalin Island in Russia, opening into the Sea of Okhotsk.
  • C. Onega
    Onega is a small town in Arkhangelsk Oblast, northwestern Russia, situated near the mouth of the Onega River on the White Sea coast.
  • D. Streletskaya Bay
    Streletskaya Bay is a smaller inlet within the larger Sevastopol Bay on the Crimean coast of the Black Sea, known for its coastal landscape and maritime use.
  • E. Zolotoy Rog Bay
    Zolotoy Rog Bay is a narrow, horn-shaped inlet in Vladivostok, Russia, serving as a major natural harbor and focal point of the city's maritime activity.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fcd5d948190b25a67a72ef980e9 completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff366bd31c81909e21075b6b601448 completed May 9, 2026, 1:28 p.m.
Created at: April 10, 2026, 3:55 a.m.