Triple

T18998081
Position Surface form Disambiguated ID Type / Status
Subject Russo-Turkish War (1735–1739) E464870 entity
Predicate outcomeForRussia P93970 FINISHED
Object gained Azov without fortifications 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: gained Azov without fortifications | Statement: [Russo-Turkish War (1735–1739), outcomeForRussia, gained Azov without fortifications]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: outcomeForRussia
Context triple: [Russo-Turkish War (1735–1739), outcomeForRussia, gained Azov without fortifications]
  • A. effectOnRussia chosen
    Indicates the impact or consequences that something has on Russia.
  • B. participantReleasedByRussia
    Indicates that a participant was freed from custody or control specifically by Russian authorities or entities.
  • C. strengthRussia
    Indicates a relationship where a level, measure, or display of strength is attributed to or associated with Russia.
  • D. successorStateOnSovietSide
    Indicates that one state is recognized as the political or legal successor to a former state that was part of the Soviet sphere or structure.
  • E. RussiaControls
    Indicates that Russia exercises authority, influence, or governing power over the specified entity or territory.
  • 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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6838f4481909b265e29964b0dca completed April 20, 2026, 7:32 a.m.
PD Predicate disambiguation batch_69e4a2f88e0c81908cb20f08bf24cd32 completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 12:01 p.m.