Triple

T6339978
Position Surface form Disambiguated ID Type / Status
Subject Dmytro E142599 entity
Predicate typicalScriptForm P70071 FINISHED
Object Дмитро E587797 NE FINISHED

How this triple was built (3 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: Дмитро | Statement: [Dmytro, typicalScriptForm, Дмитро]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Дмитро
Context triple: [Dmytro, typicalScriptForm, Дмитро]
  • A. Oleksiy
    Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
  • B. Dmytrii chosen
    Dmytrii is a masculine given name of Slavic origin, related to the Greek name Demetrius and commonly used in Eastern European cultures.
  • C. Yevhen
    Yevhen is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
  • D. Oleksandr
    Oleksandr is the Ukrainian form of the given name Alexander, commonly used in Ukraine and among Ukrainian speakers.
  • 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.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalScriptForm
Context triple: [Dmytro, typicalScriptForm, Дмитро]
  • A. typicalForm
    Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
  • B. formerScript
    Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
  • C. scriptType
    Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
  • D. writingForm
    Indicates the specific script, notation, or written representation used to express a piece of language or content.
  • E. standardFormUsedIn
    Indicates that a particular standard form is employed or applied within a given context, process, or system.
  • F. None of above. chosen

Provenance (5 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_69c008d5ab108190b346c465696824a9 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06741fbbc81908d947182b197bf59 completed March 22, 2026, 10:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69c63864d6b48190af090c1ba1487e9b completed March 27, 2026, 7:57 a.m.
PD Predicate disambiguation batch_69c060ea1a988190889e47b7e0c819b8 completed March 22, 2026, 9:36 p.m.
PDg Predicate description generation batch_69c0623bb29081908bfdfb84a07ece90 completed March 22, 2026, 9:42 p.m.
Created at: March 22, 2026, 4:30 p.m.