Triple

T13462432
Position Surface form Disambiguated ID Type / Status
Subject Maykop E311405 entity
Predicate locatedOnRiver P165 FINISHED
Object Belaya River E381149 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: Belaya River | Statement: [Maykop, locatedOnRiver, Belaya River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belaya River
Context triple: [Maykop, locatedOnRiver, Belaya River]
  • A. Belaya River
    The Belaya River is a major waterway in Russia’s Ural region, known for its scenic valleys and role as an important tributary of the Kama River.
  • B. Belaya River chosen
    The Belaya River is a significant waterway in the North Caucasus region of Russia, known for flowing through the Republic of Adygea and contributing to the Kuban River basin.
  • C. Yaga River
    The Yaga River is a mountain river in the Spanish Pyrenees that carves through the Escuaín Gorge within the Ordesa y Monte Perdido National Park.
  • D. Snezhnaya River
    The Snezhnaya River is a Siberian river in Russia that serves as one of the tributaries feeding into Lake Baikal.
  • E. Vetluga River
    The Vetluga River is a significant waterway in western Russia that flows through several regions before joining 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf0d95fc81909d9f73d5315dc7b4 completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff7559f0448190a992f0770ac8227a completed May 9, 2026, 5:56 p.m.
Created at: April 9, 2026, 9:41 p.m.