Triple

T5189753
Position Surface form Disambiguated ID Type / Status
Subject Kukarka E117121 entity
Predicate locatedOnRiver P165 FINISHED
Object Vyatka River E321320 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: Vyatka River | Statement: [Kukarka, locatedOnRiver, Vyatka River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vyatka River
Context triple: [Kukarka, locatedOnRiver, Vyatka River]
  • A. Vyatka River chosen
    The Vyatka River is a major river in western Russia that flows through the Kirov and Nizhny Novgorod regions and plays an important role in regional transport, ecology, and settlement.
  • B. Kostroma River
    The Kostroma River is a major waterway in central Russia that flows through Kostroma Oblast before joining the Volga River.
  • C. Okhta River
    The Okhta River is a tributary waterway in northwestern Russia that flows through Saint Petersburg before joining the Neva River.
  • D. Votka River
    The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
  • E. Byk River
    The Byk River is a tributary watercourse in Eastern Europe that flows through Moldova before joining the Dniester 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_69bd44620ff48190bcac01782107a397 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd79c732b48190af62dfffcbc5e3a6 completed March 20, 2026, 4:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfb1324c2c8190ba2a1c5708ba88e5 completed March 22, 2026, 9:06 a.m.
Created at: March 20, 2026, 1:46 p.m.