Triple

T8844833
Position Surface form Disambiguated ID Type / Status
Subject Volodymyr E210478 entity
Predicate formerName P65 FINISHED
Object Volodymyr-Volynskyi E210478 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: Volodymyr-Volynskyi | Statement: [Volodymyr, formerName, Volodymyr-Volynskyi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Volodymyr-Volynskyi
Context triple: [Volodymyr, formerName, Volodymyr-Volynskyi]
  • A. Volodymyr chosen
    Volodymyr is a historic city in western Ukraine known for its medieval heritage and role as a former center of the Volhynia region.
  • B. Dmytrii
    Dmytrii is a masculine given name of Slavic origin, related to the Greek name Demetrius and commonly used in Eastern European cultures.
  • C. Vasyl Borodai
    Vasyl Borodai was a Soviet and Ukrainian sculptor best known for creating monumental public works, including Kyiv’s iconic Motherland Monument.
  • D. Bohdan
    Bohdan is a masculine given name of Slavic origin, notably borne by the 17th-century Ukrainian Cossack leader Bohdan Khmelnytsky.
  • E. Roman Danylovych
    Roman Danylovych was a 13th-century Ruthenian prince from the ruling dynasty of the Kingdom of Galicia–Volhynia in Eastern Europe.
  • 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_69ca838967bc8190b46c3c80a2887ea4 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60a6623c8190ba43545544f58633 completed April 1, 2026, 12:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69cf89ad0a3c8190a2bcf9a106138835 completed April 3, 2026, 9:34 a.m.
Created at: March 30, 2026, 6:48 p.m.