Triple

T2632605
Position Surface form Disambiguated ID Type / Status
Subject Southern Front of the Russian Civil War E59668 entity
Predicate location P40 FINISHED
Object Kuban E57489 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: Kuban | Statement: [Southern Front of the Russian Civil War, location, Kuban]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuban
Context triple: [Southern Front of the Russian Civil War, location, Kuban]
  • A. 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.
  • B. Byk River
    The Byk River is a tributary watercourse in Eastern Europe that flows through Moldova before joining the Dniester River.
  • 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. Sochi River
    The Sochi River is a mountain river in Russia’s Krasnodar Krai that flows through the city of Sochi into the Black Sea.
  • 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_69ab4ac8596c8190b34997e73d9e991c completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd8c8d32c819081fc89b91217ed54 completed March 7, 2026, 7:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69afa04cf4e08190938687bfeb0ae353 completed March 10, 2026, 4:38 a.m.
Created at: March 6, 2026, 9:50 p.m.