Triple

T9953086
Position Surface form Disambiguated ID Type / Status
Subject Lubart E195376 entity
Predicate ruledTerritory P10006 FINISHED
Object Volodymyr 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 | Statement: [Lubart, ruledTerritory, Volodymyr]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Volodymyr
Context triple: [Lubart, ruledTerritory, Volodymyr]
  • 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. Oleksiy
    Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
  • C. Oleksandr
    Oleksandr is the Ukrainian form of the given name Alexander, commonly used in Ukraine and among Ukrainian speakers.
  • D. Yevhen
    Yevhen is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
  • E. Yuriy Drohobych
    Yuriy Drohobych was a 15th-century Ukrainian (Ruthenian) scholar, astronomer, physician, and rector of the University of Bologna, known as one of the earliest prominent intellectuals from the Drohobych region.
  • 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_69ca82eaaa008190a54fa1a9f954b9ad completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb693918081908e9f96ef302235ad completed April 2, 2026, 12:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2293dc93881908aff4cb3640c0edf completed April 5, 2026, 9:19 a.m.
Created at: March 30, 2026, 8:46 p.m.