Triple

T9738354
Position Surface form Disambiguated ID Type / Status
Subject Second Kuban Campaign E236122 entity
Predicate historicalRegion P915 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: [Second Kuban Campaign, historicalRegion, Kuban]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuban
Context triple: [Second Kuban Campaign, historicalRegion, Kuban]
  • 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. Berland River
    The Berland River is a tributary waterway in west-central Alberta, Canada, that flows through forested foothills before joining the Athabasca River.
  • D. Gudalovka
    Gudalovka is a rural locality in Russia notable as the birthplace of Marxist theorist Georgi Plekhanov.
  • E. Chornaya River
    The Chornaya River is a significant waterway that contributes substantially to the flow and drainage basin of the Shilka River in eastern Russia.
  • 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_69ca84d313e88190983ee6ffd0ef60d2 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9ef2ba048190811d6f4251fdb270 completed April 1, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5a1a3b88190a1b4561a9a780e41 completed April 5, 2026, 3:23 a.m.
Created at: March 30, 2026, 8:22 p.m.