Triple

T20821315
Position Surface form Disambiguated ID Type / Status
Subject Operation Vistula E512578 entity
Predicate targetedEthnicGroup P10927 FINISHED
Object Boykos 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: Boykos | Statement: [Operation Vistula, targetedEthnicGroup, Boykos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boykos
Context triple: [Operation Vistula, targetedEthnicGroup, Boykos]
  • A. Boykos chosen
    Boykos are a distinct East Slavic highlander ethnic group traditionally inhabiting the Carpathian Mountains region of western Ukraine and neighboring areas.
  • B. Kovpak
    Kovpak is a Ukrainian surname most notably associated with Sydir Kovpak, a famed Soviet partisan leader during World War II.
  • C. Kostenko
    Kostenko is a Slavic surname of Ukrainian and Russian origin borne by various notable figures in politics, military, arts, and sports.
  • D. Krutov
    Krutov is the namesake of a KLM airline route, likely a notable individual after whom the line was dedicated.
  • E. Baklanov
    Baklanov is a Russian surname most notably associated with Soviet politician and aerospace official Oleg Baklanov.
  • 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2f7a1548190b6ef3f1cfad37c1c completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:41 p.m.