Triple

T2211953
Position Surface form Disambiguated ID Type / Status
Subject Oleksandr E50936 entity
Predicate relatedName P3889 FINISHED
Object Oleksiy E146702 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: Oleksiy | Statement: [Oleksandr, relatedName, Oleksiy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oleksiy
Context triple: [Oleksandr, relatedName, Oleksiy]
  • A. Oleksiy chosen
    Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
  • B. Oleksandr
    Oleksandr is the Ukrainian form of the given name Alexander, commonly used in Ukraine and among Ukrainian speakers.
  • C. Andriy
    Andriy is a Slavic given name, equivalent to the English name Andrew.
  • D. Dmytro
    Dmytro is a common Ukrainian male given name, equivalent to "Dmitry" in Russian and derived from the Greek name Demetrios.
  • E. Mykola
    Mykola is the Ukrainian form of the given name Nicholas, commonly used in Ukraine and among Ukrainian communities.
  • 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_69a88b06709c8190978fb2418470d1b6 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abbfecea6c8190b762bbfda8490e31 completed March 7, 2026, 6:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae6af84b708190ac3170a343eb107f completed March 9, 2026, 6:38 a.m.
Created at: March 4, 2026, 7:46 p.m.