Triple

T19866827
Position Surface form Disambiguated ID Type / Status
Subject Battle of Irpin (2022) E477412 entity
Predicate locatedIn P40 FINISHED
Object Irpin 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: Irpin | Statement: [Battle of Irpin (2022), locatedIn, Irpin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Irpin
Context triple: [Battle of Irpin (2022), locatedIn, Irpin]
  • A. Irpin chosen
    Irpin is a city in northern Ukraine, located near Kyiv, known for its rapid suburban development and the heavy damage it suffered during the 2022 Russian invasion.
  • B. Puławy
    Puławy is a historic town in eastern Poland known for its classical palace-and-park complex and role as an important cultural and scientific center.
  • C. Puławy
    Puławy is a village in southeastern Poland located within the administrative district of Gmina Rymanów in the Subcarpathian Voivodeship.
  • D. Murów
    Murów is a village in southwestern Poland that serves as the seat of the rural administrative district (gmina) of Murów in Opole Voivodeship.
  • E. Krasnobród
    Krasnobród is a small town in southeastern Poland known for its historical role in World War II and as a local tourist and spa destination in the Roztocze region.
  • 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_69d8e51e7d948190aedbcd6c30361c39 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6589f9654819080597a4f7c52d64c completed April 20, 2026, 4:47 p.m.
Created at: April 10, 2026, 1:51 p.m.