Triple

T19332683
Position Surface form Disambiguated ID Type / Status
Subject Южный федеральный округ E483534 entity
Predicate containsRiver P165 FINISHED
Object Кубань 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: Кубань | Statement: [Южный федеральный округ, containsRiver, Кубань]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Кубань
Context triple: [Южный федеральный округ, containsRiver, Кубань]
  • A. Kuban
    Kuban is a Turkish surname most notably borne by the prominent architectural historian and scholar Doğan Kuban.
  • B. Kuban River chosen
    The Kuban River is a major river in the North Caucasus region of Russia that flows through the Krasnodar Krai before emptying into the Sea of Azov.
  • C. Voronezh River
    The Voronezh River is a major river in western Russia that flows through the city of Voronezh before joining the Don River.
  • D. Kazan River
    The Kazan River is a major river in the Republic of Tatarstan, Russia, flowing through the city of Kazan before emptying into the Volga River.
  • E. Gudalovka
    Gudalovka is a rural locality in Russia notable as the birthplace of Marxist theorist Georgi Plekhanov.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61642f49c81909226cfd701f7c139 completed April 20, 2026, 12:04 p.m.
Created at: April 10, 2026, 1:33 p.m.