Triple

T19968996
Position Surface form Disambiguated ID Type / Status
Subject Battle of Vasylkiv (2022) E480019 entity
Predicate location P40 FINISHED
Object Vasylkiv 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: Vasylkiv | Statement: [Battle of Vasylkiv (2022), location, Vasylkiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vasylkiv
Context triple: [Battle of Vasylkiv (2022), location, Vasylkiv]
  • A. Vasylkiv chosen
    Vasylkiv is a historic town in central Ukraine, known for its long-standing administrative role and its location near the capital city of Kyiv.
  • B. Vasylkivska
    Vasylkivska is a station on the Kyiv Metro system in Ukraine.
  • C. Petrykiv
    Petrykiv is a surname of likely Eastern European origin, associated with individuals or places bearing a similar name such as Petrykiv.
  • D. Lukianivska
    Lukianivska is a Kyiv Metro station on the Syretsko–Pecherska line serving the Lukianivka neighborhood in Ukraine’s capital.
  • E. Pervomaiskyi
    Pervomaiskyi is a small industrial city in eastern Ukraine known for its chemical industry and location within Kharkiv Oblast.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65bc7c2fc81909b89c549a5f99e4c completed April 20, 2026, 5 p.m.
Created at: April 10, 2026, 1:54 p.m.