Triple

T11501675
Position Surface form Disambiguated ID Type / Status
Subject Cossack sabers (shashka) E272677 entity
Predicate adoptedBy P1034 FINISHED
Object Terek Cossacks E274357 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: Terek Cossacks | Statement: [Cossack sabers (shashka), adoptedBy, Terek Cossacks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Terek Cossacks
Context triple: [Cossack sabers (shashka), adoptedBy, Terek Cossacks]
  • A. Terek Cossacks chosen
    The Terek Cossacks are a historic Cossack community that settled along the Terek River in the North Caucasus, serving as frontier warriors of the Russian Empire and later Russia.
  • B. Terek Grozny
    Terek Grozny is a Russian professional football club based in Grozny, Chechnya, that has competed in the Russian Premier League.
  • C. Gudalovka
    Gudalovka is a rural locality in Russia notable as the birthplace of Marxist theorist Georgi Plekhanov.
  • D. Tulskaya
    Tulskaya is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Tulskaya Square area in southern Moscow.
  • E. Terek River
    The Terek River is a major river in the North Caucasus that flows through Georgia and Russia before emptying into the Caspian 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de55cbc8190be71c2d03dc044f2 completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69e604bc1d3c81908497f1d19dcc2167 completed April 20, 2026, 10:49 a.m.
Created at: April 8, 2026, 9:36 p.m.