Triple

T19998214
Position Surface form Disambiguated ID Type / Status
Subject Ilovaisk E494250 entity
Predicate partOf P40 FINISHED
Object Donetsk Raion E897892 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: Donetsk Raion | Statement: [Ilovaisk, partOf, Donetsk Raion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Donetsk Raion
Context triple: [Ilovaisk, partOf, Donetsk Raion]
  • A. Donetsk Raion chosen
    Donetsk Raion is an administrative district in Donetsk Oblast, eastern Ukraine, that includes the city of Horlivka among its settlements.
  • B. Mariupol Raion
    Mariupol Raion is an administrative district in Donetsk Oblast in southeastern Ukraine, centered around the city of Mariupol.
  • C. Dnipro Raion
    Dnipro Raion is an administrative district in Dnipropetrovsk Oblast, Ukraine, centered around the city of Dnipro.
  • D. Kherson Raion
    Kherson Raion is an administrative district in southern Ukraine that includes the city of Kherson and its surrounding areas along the Dnieper River.
  • E. Donetsk Oblast
    Donetsk Oblast is an industrial and heavily urbanized region in eastern Ukraine, historically known for coal mining and metallurgy and currently a focal point of the Russo-Ukrainian conflict.
  • 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_69da626b2d748190886981ea90c8b2ea completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fe6827481909469129feb9aad91 completed April 20, 2026, 5:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a08e8202e748190a043ac51dc8faa01 completed May 16, 2026, 9:56 p.m.
Created at: April 11, 2026, 3:32 p.m.