Triple

T26189582
Position Surface form Disambiguated ID Type / Status
Subject Russo-Turkish War (1676–1681) E654923 entity
Predicate primaryObjectiveOfRussia P30325 FINISHED
Object secure Left-Bank Ukraine and Kiev LITERAL 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: secure Left-Bank Ukraine and Kiev | Statement: [Russo-Turkish War (1676–1681), primaryObjectiveOfRussia, secure Left-Bank Ukraine and Kiev]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryObjectiveOfRussia
Context triple: [Russo-Turkish War (1676–1681), primaryObjectiveOfRussia, secure Left-Bank Ukraine and Kiev]
  • A. importanceForRussia
    Indicates that something holds particular strategic, political, economic, or cultural significance specifically for Russia.
  • B. SovietObjective
    Indicates that the entity represents a goal, target, or strategic aim pursued by the Soviet Union.
  • C. RussianObjective chosen
    Indicates that an entity has an objective, goal, or target specifically related to Russia (e.g., Russian interests, territory, institutions, or actors).
  • D. objectiveOfUkraine
    Indicates that a particular goal, aim, or purpose is held or pursued by Ukraine.
  • E. RussoAustrianObjective
    Indicates a shared objective or goal jointly pursued by Russian and Austrian parties or forces.
  • F. None of above.

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_69ee5b469bc081908fe486453fdad810 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69fd783fed9c81909e792702636c4f1f completed May 8, 2026, 5:44 a.m.
PD Predicate disambiguation batch_69fd7788e63c81909de22fdafcfe41c0 completed May 8, 2026, 5:41 a.m.
Created at: April 26, 2026, 8:43 p.m.