Triple

T11388911
Position Surface form Disambiguated ID Type / Status
Subject Voronezh–Kastornoye offensive E269781 entity
Predicate namedAfter P63 FINISHED
Object Kastornoye E269781 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: Kastornoye | Statement: [Voronezh–Kastornoye offensive, namedAfter, Kastornoye]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kastornoye
Context triple: [Voronezh–Kastornoye offensive, namedAfter, Kastornoye]
  • A. Kastornoye chosen
    Kastornoye is a locality in Russia historically notable as the namesake and focal area of the Voronezh–Kastornoye military offensive during World War II.
  • B. Yuzovka
    Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
  • C. Nikolskoye
    Nikolskoye is a town in northwestern Russia known as part of the Saint Petersburg metropolitan area in Leningrad Oblast.
  • D. Nikolskoye
    Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
  • E. Ostashkov
    Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
  • 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_69d6aacdbc6c8190af6dc3d5f5d22836 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7fc389d4c81909515a5c8b0099c36 completed April 9, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5b813cfc48190a10d9b78953112ae completed April 20, 2026, 5:22 a.m.
Created at: April 8, 2026, 9:34 p.m.